ci: allow Hypercerts Release Bot GitHub App to bypass branch protection#67
ci: allow Hypercerts Release Bot GitHub App to bypass branch protection#67aspiers merged 1 commit intohypercerts-org:developfrom
Conversation
The release workflow needs to be able to push commits and tags directly to the repo when making a beta release. The default github-actions[bot] identity can't be added to branch protection ruleset bypass lists, so a new Release Bot GitHub App has been created which should facilitate this bypass mechanism.
|
There was a problem hiding this comment.
Pull request overview
This PR enables the Hypercerts Release Bot GitHub App to bypass branch protection rules during the release workflow. The default github-actions[bot] identity cannot be added to branch protection ruleset bypass lists, so this change introduces a GitHub App with appropriate credentials to facilitate automated releases.
Key changes:
- Add GitHub App token generation step using
actions/create-github-app-token@v1with secrets for app credentials - Update checkout action to use the generated app token for authenticated git operations
- Enable credential persistence to allow subsequent git push operations to bypass branch protection
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| - uses: actions/checkout@v6 | ||
| with: | ||
| # Persist releasebot app credentials to ensure that the push |
There was a problem hiding this comment.
The comment refers to "releasebot" but the GitHub App is called "Release Bot" (with a space). Consider using consistent naming, such as "Release Bot app credentials" to match the app name used in the PR title and description.
| # Persist releasebot app credentials to ensure that the push | |
| # Persist Release Bot app credentials to ensure that the push |
The release workflow needs to be able to push commits and tags directly to the repo when making a beta release. The default github-actions[bot] identity can't be added to branch protection ruleset bypass lists, so a new Release Bot GitHub App has been created which should facilitate this bypass mechanism.