elastic / cloudbeat / 28865590864
76%
main: 76%

LAST BUILD BRANCH: renovate/8.19-aws-sdk
DEFAULT BRANCH: main
Ran
Jobs 1
Files 245
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 76.123% (+0.02%) from 76.1%
28865590864

push

github

web-flow 
ci: remove Mergify auto-merge for version bump PRs (#7228)

## Summary

Removes the `auto-merge version bump PRs` Mergify rule from
`.mergify.yml` so GitHub's native merge queue owns merging into `main`.

## Rationale

GitHub's native merge queue is enforced on `main`. Mergify's `merge:`
action performs a **direct merge**, which bypasses the queue — GitHub
then rejects it with "GitHub refused to merge the pull request". This is
the second time this pattern has bitten:

- #5871 migrated most Mergify rules from `queue:` to `merge:` when
moving to GitHub's native queue.
- #6678 (`b035bd1f`) did the same for the version-bump rule after it
started dequeuing with `"Repository rule violations found: Changes must
be made through the merge queue"` — the same error we're seeing now on
#7225.

The `merge:` action was a stopgap that worked only until the ruleset
actually enforced the queue. Now that it does, Mergify shouldn't be
attempting the merge at all — GitHub's native auto-merge (`gh pr merge
--auto --squash` or the UI checkbox) and "Merge when ready" flow already
handle queued merges cleanly, so this rule is redundant *and* actively
harmful.

## Scope

Narrow — only removes the `auto-merge version bump PRs` rule. The
`auto-merge Renovate PRs` (line 16) and mergify-housekeeping (line 93)
rules use the same `merge:` action pattern and are latent versions of
the same bug — they'll be handled in follow-ups once they actually
surface, to keep this PR focused.

## Test plan

- [x] `.mergify.yml` still parses as valid YAML
- [x] Structural schema check: 14 remaining rules, all with valid
`name`/`conditions`/`actions`, only known Mergify actions used
(`assign`, `backport`, `close`, `comment`, `label`, `merge`, `review`)
- [x] Fork-based smoke test: gsarantid/cloudbeat#4 — git plumbing
verified end-to-end. Note: Mergify is not installed on the fork, so
behavioral verification against Mergify's service was not possible
without an interactive OAuth install; the chang... (continued)

10205 of 13406 relevant lines covered (76.12%)

15.9 hits per line

Jobs
ID Job ID Ran Files Coverage
1 28865590864.1 245
76.12
 GitHub Action Run
Source Files on build 28865590864