Skip to content

chore(ci): auto-merge release pull requests #120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
skyrpex merged 2 commits into from
Apr 1, 2026
Merged

chore(ci): auto-merge release pull requests #120

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
94995f5
chore(ci): auto-merge release pull requests
skyrpex Apr 1, 2026
bf43d6a
wip
skyrpex Apr 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions .github/workflows/release-auto-merge.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
name: Release Auto-merge

on:
schedule:
- cron: '0 9 * * 1'
workflow_dispatch:

permissions:
pull-requests: write
contents: write

jobs:
auto-merge:
name: Enable auto-merge on release PRs
Copy link
Copy Markdown
Contributor

@anisaoshafi anisaoshafi Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we rename this to upgrade/dependabot PRs or sth else? I don't immediately understand what release PRs are.

Copy link
Copy Markdown
Contributor Author

@skyrpex skyrpex Apr 1, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pull requests that this job tracks are different than the Dependabot ones. Google's release-please will create a special release PR that will remain open and up to date with the unreleased commits from the main branch. When that release PR is merged, the publish will happen.

I believe the name is on point given that explanation. WDYT?

runs-on: ubuntu-latest
steps:
- name: Enable auto-merge on release PRs
env:
GH_TOKEN: ${{ secrets.LOCALSTACK_BOT_TOKEN }}
GH_REPO: ${{ github.repository }}
run: |
gh pr list \
--label "autorelease: pending" \
--state open \
--json number \
--jq '.[].number' | \
while read -r pr; do
echo "Enabling auto-merge on PR #$pr"
gh pr merge "$pr" --auto --squash
done
Loading