GitHub Actions has a limitation where a workflow run using the default GITHUB_TOKEN will not trigger further workflow runs. This was impacting the release-please job because the release PRs created by it would not trigger the build job. This unfortunately led me to disable the build check for PRs to main, which was not ideal.
Educated by documentation for the create-pull-request action, I found a workaround for this using GitHub Apps and created the Notero Bot app for this purpose. The release-please job now uses the create-github-app-token action to create a token on behalf of Notero Bot and use that for creating the release PRs. This should hopefully result in workflows being run for these PRs, which will then allow us to re-enable the PR checks.
This PR also replaces google-github-actions/release-please-action with googleapis/release-please-action since it was recently moved.
github-actions[bot]
commented
5 months ago
GitHub Actions has a limitation where a workflow run using the default
GITHUB_TOKENwill not trigger further workflow runs. This was impacting therelease-pleasejob because the release PRs created by it would not trigger thebuildjob. This unfortunately led me to disable the build check for PRs tomain, which was not ideal.Educated by documentation for the create-pull-request action, I found a workaround for this using GitHub Apps and created the Notero Bot app for this purpose. The
release-pleasejob now uses the create-github-app-token action to create a token on behalf of Notero Bot and use that for creating the release PRs. This should hopefully result in workflows being run for these PRs, which will then allow us to re-enable the PR checks.This PR also replaces
google-github-actions/release-please-actionwithgoogleapis/release-please-actionsince it was recently moved.