Repository navigation
docs: releasing.md stands alone and asks for no required reviewer - #12
Merged
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
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.
Closes #5. Closes #6.
docs/releasing.md, section "One-time setup", now stands alone:GITHUB_TOKENor a personal token;openssl, checked on the Key pairs page;releaseenvironment made and limited tomainfirst, then the secret, then the variables; then delete the.pemfile;releaseenvironment, and why (it is used on every push tomain; the gate is the owner's merge of the release PR).Checks:
git grep -ni nodkeyfinds nothing.git grep -ni reviewerfinds only the line that says there is no required reviewer, and thesecurity-revieweragent.Progress
mainbefore the secret) and said when the owner-only merge holds.🤖 Generated with Claude Code