Skip to content

fix: centralize release auto-merge #3

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
chio-labs-delivery merged 1 commit into from
Aug 24, 2026
Merged

fix: centralize release auto-merge #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 1 addition & 2 deletions .github/workflows/auto-merge.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,7 @@ jobs:
request-auto-merge:
if: >-
!github.event.pull_request.draft &&
github.event.pull_request.head.repo.full_name == github.repository &&
!startsWith(github.event.pull_request.head.ref, 'release-please--')
github.event.pull_request.head.repo.full_name == github.repository
runs-on: ubuntu-latest
steps:
- name: Create delivery token
Expand Down
8 changes: 5 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,12 @@ This repository owns organization-wide GitHub workflow policy.
`auto-merge.yml` requests squash auto-merge for ready, same-repository pull requests. Repository
rulesets and required checks remain authoritative: GitHub merges only after every required check
passes. It uses an organization-owned GitHub App so the resulting merge can trigger downstream
delivery workflows. Release Please branches are excluded because each product's release workflow
validates those pull requests and requests auto-merge itself with the same App identity.
delivery workflows. This includes Release Please pull requests; product release workflows must use
the same App identity when creating or updating those branches so GitHub emits the pull request
events that invoke the organization workflow.

The organization ruleset applies this workflow to Chio Labs public repositories.

Draft and fork-based pull requests are intentionally excluded. A draft is handled when it becomes
ready for review. Release Please pull requests remain owned by each product's release workflow.
ready for review. Product workflows remain responsible for release-specific validation, while this
organization workflow is the single owner of requesting auto-merge.
Loading