chore: add pull request workflows for merges and releases - #9
Merged
Conversation
The release command previously assumed changes could be committed directly on main, and ordinary work had no shared command that carried it through a branch, pull request and merge. Claude and other agents could therefore follow different paths for the same repository operation, while a request to merge without releasing had no way to state that no tag should be created. Releases now move through a conventional branch and a Why/What pull request, pin CI to the proposed merge, squash into main and tag only the proved merge commit. A separate merge skill uses the same branch, PR and CI safeguards for ordinary changes and explicitly stops after the squash merge. The agent-neutral skills remain the source of truth. Small Claude command adapters expose /release and /merge without copying either workflow, and the repository guidance records when each one applies.
GitHub exposes this repository's pull-request workflow with the source branch and head commit in the Actions run metadata. Looking it up by the synthetic potential merge commit returned no run, so either merge workflow would wait for a build it could never find. Both skills now select the pull-request run by its branch and checked head OID. They still compare the head, base and potential merge OIDs after CI and pin the squash merge to that checked head.
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.
Why
The release command assumed changes could be committed directly on
main, andordinary work had no shared command for the branch, pull request and merge
path. Claude and other agents could therefore handle the same operation
differently, while “merge this” could accidentally be confused with cutting a
tagged release.
What
The release skill now creates a conventional branch, writes a Why/What pull
request, validates the proposed and merged commits, squash-merges to
main,and tags only the proved merge. A new agent-neutral merge skill applies the
same branch, PR and CI safeguards but explicitly creates no tag. Thin Claude
adapters expose both
/releaseand/mergefrom those shared instructions.