docs(claude): green PRs merge without asking — resolve the merge-rule contradiction - #10
Merged
Merged
Conversation
… contradiction The commit policy said "ask before merging a PR", which agreed with the background-job "never merge" boilerplate — while the standing feedback memory (feedback-ship-without-pr-review) said the opposite: George never opens GitHub; agents review, merge, deploy, and verify live. Every background session hit the same three-way conflict and stalled on it (overridden by hand 3x). Resolved in favor of shipping, as confirmed 2026-08-07: a CI-green, non-draft PR on a feature branch in George's own repos IS the deliberate step — the pipeline (branch + CI + review) is the gate, not a human clicking a button. Force-pushes, direct pushes to default, red/foreign PRs, deletions, and publishing beyond a normal deploy still require asking. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The commit policy said "ask before merging a PR", agreeing with the background-job boilerplate — while the standing feedback memory said the opposite (George never opens GitHub; agents review, merge, deploy, verify live). Every background session hit the same three-way conflict; it was overridden by hand 3×. Resolved 2026-08-07 in favor of shipping: a CI-green, non-draft PR on a feature branch in George's own repos IS the deliberate step. Force-pushes, direct default-branch pushes, red/foreign PRs, deletions, and publishing beyond a normal deploy still require asking.
🤖 Generated with Claude Code