docs: clarify latest-main requirement for worktrees#44
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add explicit AGENTS guidance to stay on the latest remote main, with detached worktree handling called out near the top of the file and in the pre-PR checklist.
Why
Detached worktrees make it easy to start from a stale commit. The repo guidance should state this requirement plainly where agents will see it before editing or shipping.
How
Updated
AGENTS.mdwith a top-level reminder to fetchorigin/mainand rebase or branch from it before editing in detached worktrees, and expanded the rebased-branch checklist item to mention the worktree case.Risk
Checklist