Skip to content

AGENTS.md says what a release asks of the user - #54

Merged
czj merged 1 commit into
mainfrom
tighten-agents-md
Nov 7, 2026
Merged

czj merged 1 commit into
mainfrom
tighten-agents-md

Conversation

@czj

@czj czj commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

AGENTS.md said how to release, but not what a release asks of the person running it, nor how to tell that another session had just released: two sessions working on one gem ended up unsure whether a version was out.

This pull request rewrites the Releases section and tightens the rest of the file without dropping anything.

  • Releases: the user is needed for a working git signing key and one click on the release environment; check for a release already under way first; --dry-run then --yes; bin/release --tag after an interruption; an unsigned tag is never released.
  • Same shared sections: the rules, pull request and release sections stay word for word identical in super-slim, gamba, crumbly and agentry.
  • Tighter wording: the other sections say the same in fewer words; the Releases section grows by the steps it lacked, so the file ends about 70 words longer.

@czj
czj enabled auto-merge (squash) November 7, 2026 22:34
@czj
czj merged commit 1ac645b into main Nov 7, 2026
11 checks passed
@czj
czj deleted the tighten-agents-md branch November 7, 2026 22:35
@czj czj changed the title AGENTS.md says what a release asks of the user, in fewer words AGENTS.md says what a release asks of the user Nov 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant