[workflow] chore: ignore local worktrees - #71
Conversation
|
Warning Review limit reached
More reviews will be available in 57 minutes and 50 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR ignores project-local ChangesAgent workflow guidance
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Code Review
This pull request updates the repository's configuration and documentation to support parallel agent workflows. Specifically, it adds .worktrees/ to .gitignore and updates both AGENTS.md and docs/contributing.md to instruct contributors and agents to use project-local worktrees and run local code reviews before merging. The review feedback suggests enhancing these instructions by adding concrete git worktree add command examples to make the process more explicit and easier to follow.
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.
| ### Workflow (Branches + PRs) | ||
|
|
||
| - Always branch from the latest `main` when starting a new feature or bug fix. | ||
| - Use project-local worktrees under `.worktrees/` for parallel agent work. |
There was a problem hiding this comment.
Adding a concrete command example here helps LLM agents reliably construct the correct git worktree command without guessing the path structure.
| - Use project-local worktrees under `.worktrees/` for parallel agent work. | |
| - Use project-local worktrees under .worktrees/ for parallel agent work (e.g., git worktree add .worktrees/branch-name branch-name). |
| - For parallel agent work, branch from the latest `main` and place worktrees | ||
| under `.worktrees/`. |
There was a problem hiding this comment.
To make it easier for contributors to follow this convention, it would be helpful to provide a quick example of the git worktree add command showing how to use the .worktrees/ directory.
| - For parallel agent work, branch from the latest `main` and place worktrees | |
| under `.worktrees/`. | |
| - For parallel agent work, branch from the latest main and place worktrees | |
| under .worktrees/ (e.g., git worktree add .worktrees/feature-branch feature-branch). |
|
Addressed the review suggestion by adding concrete project-local worktree commands in both |
Summary
.worktrees/so project-local agent worktrees do not pollute git status..worktrees/convention inAGENTS.mdand contributor guidance.Test Plan
mkdocs buildpre-commit run --all-filesSummary by CodeRabbit