Skip to content

Conversation

@MoonBoi9001
Copy link
Member

@MoonBoi9001 MoonBoi9001 commented Jan 17, 2026

Summary

Branch protection requires signed commits, but github-actions[bot] commits aren't GPG signed.

In PR #98 (created by the github-actions bot) we see that:

Merging is blocked
Commits must have verified signatures.

This fix for this uses iarekylew00t/verified-bot-commit which creates commits via the GitHub API, resulting in signed commits that can be merged.

This requuires using verified-bot-commit action, however the issue is that composite actions can only use run: steps - they cannot use uses: to call other actions. This meant that we had to move the commit/push/PR logic from the composite action to the workflow as part of this PR.


Generated with Claude Code

Branch protection requires signed commits, but github-actions[bot] commits
aren't GPG signed. This uses iarekylew00t/verified-bot-commit which creates
commits via the GitHub API, resulting in automatically verified commits.

Changes:
- Add branch-name and pr-exists outputs to sync-manifest action
- Move commit/push/PR logic from action to workflow (required because
  composite actions cannot use 'uses:' to call other actions)
- Use verified-bot-commit to create signed commits via GitHub API

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@MoonBoi9001 MoonBoi9001 marked this pull request as ready for review January 19, 2026 20:17
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.

2 participants