merge queue: embarking main (b67f298) and #7 together - #9
Closed
mergify[bot] wants to merge 2 commits into
Closed
Conversation
Bumps [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) from 5.15.3 to 5.16.15. - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/astro@5.16.15/packages/astro) --- updated-dependencies: - dependency-name: astro dependency-version: 5.16.15 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
jd
added a commit
that referenced
this pull request
Aug 7, 2026
GitLab users call it a merge train, GitHub users call it a merge queue, and the Academy had no page explaining that these are the same technique with different defaults. This adds one. Why this topic, from the evidence gathered while picking the next two lessons (see marketing/efforts/merge-queue-academy.md in the ops repo): - It is the only merge-queue-adjacent term family with real search demand. DataForSEO (US, desktop): "merge train" 110/mo, "merge train gitlab" 90, "merge trains" 50, plus a long tail. Every other long-tail merge queue term we tested returns 0. - Our entire estate has zero pages on it. One passing mention in a blog post, nothing else on mergify.com, docs, or the Academy. - The live SERP is weak: Stack Overflow #3, a Hacker News thread #4, a Medium post #16. The only real comparison page is Graphite's at #9, and it is what Google's AI Overview cites on both "merge train" and "merge train vs merge queue". - The page is self-canonical. It does not overlap the seven Academy pages that canonical into mergify.com/learn/merge-queue, and it does not collide with the /learn/merge-queue guides cluster planned as P5 in marketing/efforts/rank-merge-queue.md. Content is sourced from GitLab and GitHub documentation, cited at the bottom of the page: merged results pipelines and their parallel construction, the drop-and-restart-behind failure behaviour with no retry, the 20-pipelines-per- train default cap, the Premium/Ultimate tier requirement, and GitHub's merge_group batching with configurable min/max group size. Also adds a "Merge Train" glossary entry and a homepage card. Change-Id: Ieb6657423f9aa83270edc28b59a3d2329a4716cc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎉 This pull request has been checked successfully and will be merged soon. 🎉
Branch main (b67f298) and #7 are embarked together for merge.
This pull request has been created by Mergify to speculatively check the mergeability of #7.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.
Required conditions of queue
defaultfor merge:No extra conditions.
Required conditions to stay in the queue: None