Repository navigation
merge queue: checking #13254 on main (d6e5e52), stacked on #13253 - #13266
Closed
mergify[bot] wants to merge 4 commits into
Closed
mergify[bot] wants to merge 4 commits into
mergify[bot] wants to merge 4 commits into
Conversation
Mergify's test product is now called Test Engine, the name the website uses since Mergifyio/mergify.com#823. This renames it everywhere a docs reader sees it: page titles and descriptions, headings, prose, the sidebar and home page cards, the API reference section label, llms.txt, the structured data description and the CI upload components. The overview page says "formerly Test Insights" once, so a reader who arrives with the old name knows they are in the right place. Every URL stays the same (`/test-insights/...`, `/api/test-insights`), so no redirect is needed. Renaming a heading changes its anchor, and the two internal links to a renamed heading are updated: `/integrations/slack#test-engine-notifications` and `/enterprise/advanced-features/#ci-insights-and-test-engine-object-storage`. Left as they are, on purpose: - the skip message the rspec-mergify gem prints (`Test is quarantined from Mergify Test Insights`), quoted verbatim because readers match on it; - changelog entries, which keep the product tag they were published with. The changelog accent map now knows both names; - the pinned copy of the gha-mergify-ci action.yml and the synced API schema, which follow their upstreams; - identifiers that only look like the name: the icon id, CSS classes and file names. The three Test Engine screenshots and the Merge Queue statistics screenshot still show the old name in the dashboard. They will be recaptured once the dashboard shows the new one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Change-Id: I4b980a1639fa5d71310c79106e250a4656fd8217
…in protections shots The Merge-After screenshot on the built-in protections page showed `Merge-After: 2023-12-25T00:00`, a date long past, on a page that says the header delays merging until a future time. The text example above it had the same problem with `2025-09-01T09:00:00Z`. Both screenshots on the page are reshot as a matched pair on a public sandbox repository, in the same dark theme and framing as before: - `merge-after.png` now carries `Merge-After: 2030-12-25T00:00`. - `depends-on.png` is recaptured alongside it so the two still look alike on the page (`Depends-On: #1`). The text example moves to `2030-09-01T09:00:00Z`. The images are now captured at 2x, so they render sharper on high-density screens. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Change-Id: I91686e32e33ef6245cb128828f5169b8059fe334
This branch was successfully deployed
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
1 participant
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. 🎉
#13254 is queued for merge on branch main (d6e5e52).
Stacked behind 1 pull request queued ahead of this batch, not part of it. These checks run on a tip that also carries its commits, so a failure here can come from it as much as from #13254.
Queued ahead of this batch:
This pull request has been created by Mergify to speculatively check the mergeability of #13254.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.
Required conditions of queue rule
defaultfor merge:github-review-approved[🛡 GitHub repository ruleset ruleRequire pull request for default branch]schedule=Mon-Fri 09:00-17:30[Europe/Paris]Enforce conventional commit]:title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:👀 Review Requirements]:#approved-reviews-by >= 1author = dependabot[bot]author = renovate[bot]author = mergify-ci-bot-head ~= ^docs-agent/📕 PR description]:body ~= (?ms:.{48,})🔎 Reviews]:#changes-requested-reviews-by = 0#review-requested = 0#review-threads-unresolved = 0Required CIs]:check-success = @github-actions/gatecheck-neutral = @github-actions/gatecheck-skipped = @github-actions/gateRequired conditions to stay in the queue:
github-review-approved[🛡 GitHub repository ruleset ruleRequire pull request for default branch]Enforce conventional commit]:title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:👀 Review Requirements]:#approved-reviews-by >= 1author = dependabot[bot]author = renovate[bot]author = mergify-ci-bot-head ~= ^docs-agent/📕 PR description]:body ~= (?ms:.{48,})🔎 Reviews]:#changes-requested-reviews-by = 0#review-requested = 0#review-threads-unresolved = 0author != dependabot[bot]author != mergify-ci-botauthor != renovate[bot]head ~= ^docs-agent/Required CIs]:check-success = @github-actions/gatecheck-neutral = @github-actions/gatecheck-skipped = @github-actions/gate