📝 docs: add Branching & PR workflow to AGENTS.develop.md template#126
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.
Mirrors the section added to
AGENTS.mdin PR #125 intoAGENTS.develop.md— the develop-branch reference that the post-checkout hook copies toAGENTS.mdfor every new feature branch.Why: without this in the template, the rule does not propagate to new branches, so the
master-vs-developPR-target mistake will recur.Same documented rules:
develop; ALL PRs--base develop, nevermastermasteronly receives release merges fromdevelop--merge), not squashgh pr merge <n> --merge --admin --delete-branchgh pr view <n> --json baseRefName; retarget if neededDocs-only. No code impact.