Repository navigation
chore: ignore release-script temporary commit message - #1451
Open
copystring wants to merge 3 commits into
Open
copystring wants to merge 3 commits into
copystring wants to merge 3 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Summary
.commitmessage, which@alcalzone/release-scriptcreates and removes during operation..commitmessagefiles stay ignored.This is a narrow safety fix. No version change, release run, tag, publish, or merge is included. The required isolated
--dry --noPush --branch-patternproof could not be run in this workspace: its checkout is empty and the provided git launcher fails withPaperclip: requested GitHub command is not installed.I did not invoke release-script in the working checkout.After this fix is merged, a release PR should be based on current final
mainand contain only the release commit. The semantic tag must then be created against the final merged main SHA; pushing that tag triggers the deploy job intest-and-release.yml.