Open one auto-merging PR per package from every sync workflow
sync-upstream.yml, sync-rebuilds.yml and track-branches.yml each opened one batch PR, so one package with a failing build held back every other update in it (#788, #837). All three now group their changes with package-pr-groups.sh and hand them to package-prs.yml, which opens a PR per package and arms auto-merge. Packages pinned from the same upstream branch still share one. Green packages land on their own and only the failures stay open; a red PR conflicting with master, and each lane's old batch PR, get closed. sync-upstream.yml loses its human-merged lane: it now pushes with the PAT like the other two, so its builds start without an approval hold and its PRs auto-merge when green. min_release_age still quarantines fresh releases. Its approve job, approve-sync-push.cjs, and auto-merge-pr.cjs's exception for auto/sync-upstream go with it.
This commit is contained in:
1 parent
a7f730d1e6
commit
ba7561a34c
11 files changed
+424
-467
No files matched your search
@@ -37,7 +37,8 @@ A dependency this repository carries for an architecture (a recipe here that bui
|
||||
|
||||
## The workflow
|
||||
|
||||
`sync-rebuilds.yml` runs `bin/sync-rebuilds` every 6 hours, opens one PR on
|
||||
`auto/sync-rebuilds` and enables auto-merge. The PR lands once `result`,
|
||||
`self-tests` and `build-isolation` pass, and the merge publishes. A rebuild that
|
||||
fails stays an open red PR for a maintainer.
|
||||
`sync-rebuilds.yml` runs `bin/sync-rebuilds` every 6 hours and opens one PR per
|
||||
package on `auto/sync-rebuilds-<package>` with auto-merge enabled. Each PR lands
|
||||
once `result`, `self-tests` and `build-isolation` pass, and the merge publishes.
|
||||
A rebuild that fails stays an open red PR for a maintainer without holding back
|
||||
the others.
|
||||
Reference in new issue
Block a user