Skip to content

merge queue: checking #7605 on main (4bbd1df), stacked on #7561 and #7604 - #7643

Closed
mergify[bot] wants to merge 6 commits into
mainfrom
mergify/merge-queue/d5b730d170
Closed

mergify[bot] wants to merge 6 commits into
mainfrom
mergify/merge-queue/d5b730d170

Conversation

@mergify

@mergify mergify Bot commented Sep 21, 2026

Copy link
Copy Markdown

⏳ The pull request #7605 is queued for merge and currently being checked. ⏳

#7605 is queued for merge on branch main (4bbd1df).

Stacked behind 2 pull requests queued ahead of this batch, not part of it. These checks run on a tip that also carries their commits, so a failure here can come from them as much as from #7605.

Queued ahead of this batch:

  • #7561 — shares the scope app
  • #7604 — shares the scope app
1 scope
  • app

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

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

Queue graph

The diagram is not laid out in queue order, so a node's position says nothing about when it merges.

graph LR
    a037466ededb4b34a64f674fc14407eb["loyal-reblochon-qihxln<br/>#7561<br/>scopes: app"]
    a534b71d73f1467b8ca233b76e71db65["advanced-munster-bcizij<br/>#7604<br/>scopes: app"]
    f365994f348e4d648e43f8a88f09e3f0["national-pesto-i2i1y8<br/>#7605<br/>scopes: app"]
    a037466ededb4b34a64f674fc14407eb --> a534b71d73f1467b8ca233b76e71db65
    a534b71d73f1467b8ca233b76e71db65 --> f365994f348e4d648e43f8a88f09e3f0
    style f365994f348e4d648e43f8a88f09e3f0 fill:#6366f1,color:#fff
Loading
---
checking_base_sha: 011309f56b239af6ede980ba56e3a589cf374e96
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 7605
    scopes:
      - app
scopes:
  - app
...

lbellows and others added 6 commits September 15, 2026 08:04
The content sync stamped every scanned file with modified_at = now and
upserted it, so an idle rescan rewrote every row in the instance even when
nothing on disk had changed. Keep the stored stamp when the file is
unchanged, and skip the upsert when the row already matches.
@github-actions

Copy link
Copy Markdown
Contributor

Pull request changelog

App

Added

Changed

Deprecated

Removed

Fixed

Security

Website

Added

Changed

Deprecated

Removed

Fixed

Security

Hosting

Added

Changed

Deprecated

Removed

Fixed

Security

@mergify mergify Bot closed this Sep 21, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/d5b730d170 branch September 21, 2026 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants