Skip to content

chore: gitignore Obsidian/Claudian 볼트 루트(content/) 추가#101

Merged
CaesiumY merged 1 commit into
mainfrom
chore/gitignore-content-vault
Jul 1, 2026
Merged

chore: gitignore Obsidian/Claudian 볼트 루트(content/) 추가#101
CaesiumY merged 1 commit into
mainfrom
chore/gitignore-content-vault

Conversation

@CaesiumY

@CaesiumY CaesiumY commented Jul 1, 2026

Copy link
Copy Markdown
Owner

Description

단수 content/(Obsidian/Claudian 볼트, git 미추적 노트 사본)가 untracked로 ~140개 노출되어 (1) git status/IDE 노이즈, (2) git add -A 시 볼트 전체가 커밋될 footgun을 유발했습니다. 이 볼트는 앞선 블로그 유실 사고(경로 혼동 content/ vs contents/)의 당사자이기도 합니다. 루트 고정 /content/로 볼트만 무시합니다.

⚠️ 안전: 블로그는 무시되지 않습니다

  • contents/(복수, s 있음) = 실제 블로그 게시글(Astro 빌드 대상). 무시 대상 아님, 그대로 유지.
  • content/(단수, s 없음) = Obsidian 볼트(별도 사본, git 추적 0개). 이것만 무시.
  • /content/는 이름이 정확히 content인 디렉터리만 매칭 → contents(다른 이름)는 매칭 불가.

검증: git check-ignore content/blog = 매칭, contents/blog = 매칭 없음, contents/blog/*.md 64개 유지.

Types of changes

  • Others (repo 위생: .gitignore)

Checklist

  • Breaking Change

단수 content/(Obsidian 볼트, git 미추적 사본)가 untracked로 ~140개
노출되어 노이즈 + git add -A 시 실수 커밋 위험(블로그 유실 사고의 당사자).
루트 고정 /content/ 로 볼트만 무시.

⚠️ 복수 contents/(실제 블로그)는 이름이 달라 매칭되지 않음 — 검증 완료:
git check-ignore contents/blog = 매칭 없음, content/blog = 매칭됨. 블로그 추적 .md 64개 유지.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the .gitignore file to ignore the /content/ directory, which is used as an Obsidian/Claudian vault root, while ensuring the actual blog directory contents/ is not ignored. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@claude

claude Bot commented Jul 1, 2026

Copy link
Copy Markdown

Review

Small, well-scoped change — .gitignore diff only, 2 lines added.

Correctness

  • Verified the anchoring claim: /content/ is root-anchored (leading /) and directory-only (trailing /). Git's gitignore matching is component-exact, not prefix-based, so this pattern matches only a top-level directory literally named content and does not match contents/ (confirmed no accidental prefix overlap).
  • git ls-files | grep '^content/' returns 0 — no currently-tracked files live under content/, so this is purely a "stop showing untracked noise" change with no risk of silently un-tracking real content.
  • Grepped astro.config.ts / content.config.ts / build scripts for any reference to a root content/ path — none found, so no build-time dependency on that directory.

Code quality

  • Follows the existing style in the file: inline Korean comment explaining why, consistent with the .obsidian//.claudian/ entries directly above it. Good placement (grouped with the related vault-ignoring entries).
  • The comment explicitly calls out the singular/plural distinction with a ⚠️, which is valuable given the PR description mentions a prior incident of content/ vs contents/ path confusion — this guards future readers from repeating that mistake.

Bugs / Security / Performance

  • None applicable — this is a repo-hygiene-only change (ignore rule), no runtime code touched.
  • Arguably a minor positive for privacy/security: prevents accidentally staging personal Obsidian vault notes via git add -A.

Test coverage

  • N/A for a .gitignore-only change; no existing test would exercise this. The PR description's manual verification steps (git check-ignore content/blog matches, contents/blog doesn't, 64 blog .md files unaffected) are sufficient evidence here.

No blocking issues. LGTM.

@CaesiumY CaesiumY merged commit 401563d into main Jul 1, 2026
4 checks passed
@CaesiumY CaesiumY deleted the chore/gitignore-content-vault branch July 1, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant