Skip to content

ci: configure Graphite queue optimization - #47

Merged
graphite-app[bot] merged 1 commit into
mainfrom
ci/graphite-merge-queue
Jul 12, 2026
Merged

ci: configure Graphite queue optimization#47
graphite-app[bot] merged 1 commit into
mainfrom
ci/graphite-merge-queue

Conversation

@anandpant

Copy link
Copy Markdown
Contributor

No description provided.

Copy link
Copy Markdown
Contributor Author

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • fast-track - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@graphite-app

graphite-app Bot commented Jul 12, 2026

Copy link
Copy Markdown

Merge activity

@graphite-app
graphite-app Bot force-pushed the ci/graphite-merge-queue branch from 5901410 to 61a9aba Compare July 12, 2026 23:18
@graphite-app
graphite-app Bot merged commit 61a9aba into main Jul 12, 2026
9 checks passed
@graphite-app
graphite-app Bot deleted the ci/graphite-merge-queue branch July 12, 2026 23:19
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.

1 participant