Skip to content

add worktrees to gitignore - #274

Open
taran-p wants to merge 1 commit into
minio:mainfrom
taran-p:gitignore
Open

taran-p wants to merge 1 commit into
minio:mainfrom
taran-p:gitignore

Conversation

@taran-p

@taran-p taran-p commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Chores
    • Updated repository handling to exclude local development worktree files from version control. This maintenance change does not alter application features or behavior.

@coderabbitai

coderabbitai Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: f43b7160-22c7-4766-b021-4903eb187bef

📥 Commits

Reviewing files that changed from the base of the PR and between f27ad72 and 6bcb75f.

📒 Files selected for processing (1)
  • .gitignore

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The .gitignore file now excludes the .claude/worktrees/ directory from version control.

Changes

Git Ignore Update

Layer / File(s) Summary
Add Claude worktrees ignore rule
.gitignore
Adds .claude/worktrees/ as an ignore rule.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 6bcb7

This change keeps Claude worktrees out of version control and presents no material merge-readiness risk.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the change to add the worktrees directory to .gitignore.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit marks a path unseen
Where Claude worktrees stay serene
Git skips the burrows tucked away
One new rule keeps them at bay
Then hops along to greet the day

Comment @coderabbitai help to get the list of available commands.

@klauspost klauspost left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Not an expert, but is that a "fixed" location, or just where claude happened to create a worktree for you?

@taran-p

taran-p commented Sep 25, 2026

Copy link
Copy Markdown
Contributor Author

Not an expert, but is that a "fixed" location, or just where claude happened to create a worktree for you?

.claude/worktrees is the default location when worktrees are created when running claude via claude --worktree or in the desktop app checking the worktree option before creating, and is created programmatically, not by LLM Claude. The default can be changed, but adding this avoids this by default and it is gitignored in many of our other repos.

@harshavardhana

Copy link
Copy Markdown
Member

Not an expert, but is that a "fixed" location, or just where claude happened to create a worktree for you?

it is a fixed location in general.

Comment thread .gitignore
@@ -23,3 +23,4 @@ stage/
config.json
*.prof
*.pprof

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We should also add .claude/*.json

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.

3 participants