Repository navigation
ci: sign catalog update commits so they satisfy the main ruleset - #19
Merged
Merged
Conversation
The main branch ruleset requires signed commits. peter-evans/create-pull-request pushes unsigned commits by default, so every weekly update-catalog PR was blocked at merge despite passing CI and review (e.g. #18). sign-commits: true makes the action create commits via the GitHub API, which signs them as github-actions[bot].
dangrondahl
enabled auto-merge (squash)
August 11, 2026 11:13
JonJagger
approved these changes
Aug 11, 2026
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
2 participants
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.
The
mainruleset requires signed commits.peter-evans/create-pull-requestpushes unsigned commits by default, so every weeklyupdate-catalogPR is blocked at merge even after passing CI and review — #18 is the current example (verified: false,reason: "unsigned").