feat: add reusable auto-merge-release-pr workflow - #83
Merged
Conversation
Auto-merges the release-please PR (labeled 'autorelease: pending') once its checks pass, using a GitHub App token instead of the default GITHUB_TOKEN so the downstream push-triggered release workflow on main still fires and creates the tag/GitHub Release.
sebastiancorrea81
pushed a commit
to nullplatform/services-postgresql-rds
that referenced
this pull request
Jul 28, 2026
…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.
4 tasks
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
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
workflow_call) that auto-merges thechore(main): release x.y.zPR opened byrelease-please-action, once the PR's checks pass.secrets.app-id/secrets.app-private-key) instead of the defaultGITHUB_TOKEN. Actions' loop-prevention means a merge/push done with the default token does not trigger other workflows — so the existing push-triggered release workflow (e.g.tofu-release) would never fire and the tag/GitHub Release would never be created. An App-minted token doesn't have that restriction.release_pr_label,release_pr_author,merge_method) so it works across repos regardless of naming/merge-style differences, rather than hardcoding one repo's conventions.How it works
pull_request(opened/synchronize/labeled).release_pr_author(defaultgithub-actions[bot]) and it carries therelease_pr_label(defaultautorelease: pending) — both set automatically byrelease-please-action.gh pr checks --watch --fail-fast), then merges usingmerge_method(defaultmerge).Example caller usage
```yaml
name: auto-merge-release-pr
on:
pull_request:
types: [opened, synchronize, labeled]
jobs:
automerge:
uses: nullplatform/actions-nullplatform/.github/workflows/auto-merge-release.yml@main
secrets:
app-id: ${{ secrets.APP_RELEASE_ID }}
app-private-key: ${{ secrets.APP_RELEASE_PRIVATE_KEY }}
```
Test plan
services-postgresql-rds(ci: auto-merge release-please PRs services-postgresql-rds#5) to call this reusable workflow.