Repository navigation
Tell agents that releases wait for owner approval - #206
Merged
Merged
Conversation
The repo had no instruction file and its release process was written down nowhere: a release is a version bump, a v* tag, a GitHub Release and a manual gem push. With nothing saying stop, an agent asked to "do a release" or tidy up after a merge could tag and publish a version nobody approved, and RubyGems never lets a version number be reused. Add a short CLAUDE.md with the real check command (script/cibuild, which needs LibreOffice), the .github files synced from shared-community-files, and a Releasing section that describes what a release consists of and says only the owner ships one. Co-Authored-By: Claude Opus 5.5 <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.
Adds a short
CLAUDE.md(the repo had no instruction file) with the check command (script/cibuild, which needs LibreOffice), the.githubfiles synced from shared-community-files, and a Releasing section that writes down what a release is (version bump,vX.Y.Ztag, GitHub Release,gem push) and says agents may open a version-bump PR but never tag, push the gem, or create a GitHub Release.Why: there's no release script, so the process lived nowhere an agent could read, and nothing said to stop before tagging or publishing. RubyGems never lets a version number be reused, so an unapproved release can't be cleanly undone.
🤖 Generated with Claude Code