Skip to content

Document cleanup of merged GitHub branches #142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rmcdaniel merged 1 commit into from
Sep 27, 2026
Merged

Document cleanup of merged GitHub branches #142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,8 +65,11 @@ but they must not replace these project-wide rules.
repository's existing patterns before introducing an abstraction.
5. Let repository GitHub Actions run the normal repeatable checks. Fix failures
on the same PR unless the PR itself is fundamentally wrong.
6. Merge through GitHub after required checks pass. Publish and deploy through
the owning repository's protected workflow or documented deployment path.
6. Merge through GitHub after required checks pass. Delete the merged pull
request's remote head branch when it is no longer needed, and verify it is
absent from GitHub. Preserve branches needed for active follow-up, releases,
or maintenance. Publish and deploy through the owning repository's protected
workflow or documented deployment path.
7. Close the issue only after its acceptance criteria and user-visible outcome
are complete. Link the merged PR, published artifact, deployment, or
conformance result that proves completion.
Expand Down
Loading