Skip to content

merge queue: checking release/v3.8.49 (fd468b5), #7125 and #7501 together - #7513

Closed
mergify[bot] wants to merge 7 commits into
release/v3.8.49from
mergify/merge-queue/1b59bb9454
Closed

mergify[bot] wants to merge 7 commits into
release/v3.8.49from
mergify/merge-queue/1b59bb9454

Conversation

@mergify

@mergify mergify Bot commented Jul 16, 2026 •

Copy link
Copy Markdown

✨ Pull request #7125 ahead in the queue was removed (reason: checks failed). The pull request #7501 has been requeued. ✨

Branch release/v3.8.49 (fd468b5), #7125 and #7501 are queued together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #7501.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule release for merge:

  • #check-pending=0
  • #check-success>=1
  • check-success=Merge integrity (changelog + generated skills)
  • any of:
    • #check-failure=0
    • all of:
      • #check-failure=1
      • check-failure=dast-smoke

Required conditions to stay in the queue:

---
checking_base_sha: afdc99890eb2168f30066fb0c6e71d7a4aff56a3
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 7501
    scopes: []
scopes: []
...

Wibias and others added 7 commits July 14, 2026 03:56
…ke merge-base)

With --depth=1 the base ref is grafted, so 'git diff base...HEAD' resolves a
wrong merge-base for PR branches that recently merged the release branch. The
three-dot diff then attributes ALREADY-MERGED sibling PRs' changes to the PR
under test, producing false high-signal reds (deleted test files / weakened
asserts that exist in no ref reachable from the PR).

Observed live on #7329: the job blamed it for tests/unit/ui/provider-plan-config.test.tsx
(deleted by an unrelated merged PR) and for #7106's antigravity files. Local
reproduction with full history returns PASS for the same head.

The job's checkout is already fetch-depth: 0, so the full base fetch only
updates the ref — negligible cost.
@mergify mergify Bot closed this Jul 16, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/1b59bb9454 branch July 16, 2026 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants