ci: auto-merge release-please PRs - #5
Merged
Conversation
Merging with the default GITHUB_TOKEN would not trigger the downstream push-triggered release workflow (GitHub's Actions loop-prevention). Using a token minted from the App avoids that, so the release tag/GitHub Release gets created automatically right after this auto-merge.
4 tasks
…orkflow Replaces the inline logic with a call to the new auto-merge-release.yml reusable workflow (nullplatform/actions-nullplatform#83), so the same logic can be reused across other module repos.
This was referenced Jul 28, 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
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
chore(main): release x.y.zPR opened by release-please, once its required checks pass.auto-merge-release.yml), so the same automation can be reused by other module repos instead of duplicating it per-repo.APP_RELEASE_ID/APP_RELEASE_PRIVATE_KEY, org-level secrets) instead of the defaultGITHUB_TOKEN, because merges/pushes made with the default Actions token don't trigger other workflows — the existingrelease.yml(push tomain) would never fire and the tag/GitHub Release would never get created.Depends on
@mainon that repo).How it works
pull_request(opened/synchronize/labeled).github-actions[bot]and it carries theautorelease: pendinglabel (both set byrelease-please-actionon its release PR).branch-validation,conventional-commit,shellcheck,trivy) to go green, then merges with a regular merge commit (matches how past release PRs — e.g. chore(main): release 0.0.2 #4 — were merged).Test plan
APP_RELEASE_ID/APP_RELEASE_PRIVATE_KEYorg secrets are visible to this repo (org secret visibility set to "All repositories" or includes this repo).main) and confirm it gets auto-merged and a new tag/GitHub Release is created without manual intervention.