Repository navigation
docs: every commit and push is asked for first - #45
Merged
Merged
Conversation
Nothing is committed or pushed without the owner's permission - every change, every time, with no exemptive category. Approval of the work is not approval to land it; a green check is not an instruction. Agent briefs must say 'propose, do not commit', since a brief ending 'commit and push' overrides the rule by accident. Also records the two rules a damaged file taught: an edit that fails can still truncate the file it targeted, and a path must never be staged on the strength of intending to change it.
Contributor
CI report
Ref: |
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
Adds the permission rule to
docs/releasing.md, and the two rules that a damaged file taught.Nothing is committed or pushed without the owner's permission — every change, every time, with no exemptive category. Approval of the work is not approval to land it, and a green CI check is not an instruction. Agent briefs must say "propose, do not commit", because a brief ending "commit and push" overrides the rule by accident — which is exactly how the agent-driven work in this repository was operating.
Recorded alongside it, because they caused real damage: a failed edit can still truncate the file it targeted, and a path must never be staged on the strength of intending to change it. Both happened here — a
method.mdwas emptied by an edit that reported no match, then committed because it was staged on intent.Why it belongs in this repo
The repository's own conventions document is
docs/releasing.md, which already covers how changes reachmainand how releases are cut. A rule about not committing without permission is the same kind of convention, and it governs the workflow every contributor and agent here uses.Checks
Documentation only — no runtime surface.
bun run lint:pr-titlepasses on this title.