Repository navigation
Commit cc5be7d
authored
chore(renovate): let renovate gate its own automerge on CI (#1515)
main has no required status checks, so GitHub's auto-merge merges the moment
it is enabled - that is how #1509 landed mid-CI. platformAutomerge hands
renovate's automerge to that same mechanism, which would merge dependency
PRs before their checks report.
Requiring the new `ci gate` check on main would fix it for every merge path
at once, but a repository ruleset cannot list the built-in GitHub Actions
integration as a bypass actor:
Actor GitHub Actions integration must be part of the ruleset source or
owner organization
and required status checks reject direct pushes too, so the rule would break
update-pricing.yaml's push to main. Bypassing by write role does not help
either, because renovate holds write and would bypass the gate it is meant
to obey.
With platformAutomerge off, renovate merges the branch itself once it has
seen the branch checks pass, which needs no repository rules at all.1 parent d500f5f commit cc5be7d
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5 | 5 | | |
6 | 6 | | |
7 | 7 | | |
8 | | - | |
| 8 | + | |
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| |||
0 commit comments