merge queue: embarking main (7dc9dd9), #11453 and #11442 together#11461
Closed
mergify[bot] wants to merge 4 commits into
Closed
merge queue: embarking main (7dc9dd9), #11453 and #11442 together#11461mergify[bot] wants to merge 4 commits into
mergify[bot] wants to merge 4 commits into
Conversation
…ters Four small UX fixes for day-2 readers — users already in the docs looking for information. - Lower the top-nav breakpoint from 87em (1392px) to 68em (1088px) so the 5 nav buttons (Dashboard, Slack, Discussions, Changelog, Status) are visible at typical laptop widths. The previous breakpoint dated from when the navbar carried a logo eating the horizontal space; the logo now lives in the left sidebar. - Hub-page light heroes: /merge-queue, /ci-insights, /test-insights H1s now render in their product accent color (teal / purple / orange). Driven by a new optional `hubAccent: true` frontmatter field on the docs schema; PageContent.astro reads it and adds a `hero-accent` class to the auto-rendered H1. CSS hooks the class into the existing `--section-accent` custom property. No new copy, no screenshots, no CTAs — just an accent on the title. - Right-sidebar page-actions cluster: the right column now hosts a PageFeedback widget beneath the table of contents, giving the sidebar a purpose on short doc pages. PageFeedback is mirrored, not moved — the article-footer copy still renders for users on viewports below 82em (where the right sidebar is hidden), with a CSS rule on MainLayout hiding the footer copy when the sidebar is visible. PageMeta's existing Edit-on-GitHub link stays as the single source of truth (no duplication). - Drop the global h2 auto-numbering. The CSS counter that prefixed every h2 with 1., 2., 3. is deleted. The pattern was an Astro Starlight inheritance that doesn't fit reference / conceptual pages; sequential pages can author explicit numbering inline. The homepage h2s' `class="no-counter"` opt-outs are removed since the rule they overrode is gone. Stale `counter-increment: none` guards in changelog and api-reference styles also removed. Change-Id: Ib39618f6b4e3fc79ade43934a3d5db6faad6a551
…rage Lead with IAM role discovery / Application Default Credentials in both the S3 and GCS sections so self-hosted operators land on the path that avoids manual key rotation. Move AWS_ACCOUNT_ID/AWS_REGION and the MERGIFYENGINE_AWS_* deprecation note into the access-key option, since neither is needed when boto3 resolves credentials from the workload. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Change-Id: Idb1bb865a7b671c6e002eeeffb4f322f11dadb6c
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
2 participants
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 (7dc9dd9), #11453 and #11442 are embarked together for merge.
This pull request has been created by Mergify to speculatively check the mergeability of #11442.
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:schedule=Mon-Fri 09:00-17:30[Europe/Paris]title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?:#approved-reviews-by >= 2author = dependabot[bot]author = mergify-ci-botbody ~= (?ms:.{48,})#changes-requested-reviews-by = 0#review-requested = 0#review-threads-unresolved = 0check-success = buildcheck-success = lintcheck-success = testcheck-success = test-broken-linkslabel = ignore-broken-linkscheck-success=Cloudflare Pages-head-repo-full-name~=^Mergifyio/Required conditions to stay in the queue:
author != dependabot[bot]author != mergify-ci-bottitle ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?:#approved-reviews-by >= 2author = dependabot[bot]author = mergify-ci-botbody ~= (?ms:.{48,})#changes-requested-reviews-by = 0#review-requested = 0#review-threads-unresolved = 0check-success = buildcheck-success = lintcheck-success = testcheck-success = test-broken-linkslabel = ignore-broken-linkscheck-success=Cloudflare Pages-head-repo-full-name~=^Mergifyio/