docs(integrations): rename Monorepo CI to Job Selection - #12860
Open
jd wants to merge 1 commit into
Conversation
Contributor
Merge Protections🔴 1 of 5 protections blocking · waiting on 👀 reviews
🔴 👀 Review RequirementsWaiting for
This rule is failing.
Show 4 satisfied protections🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
There was a problem hiding this comment.
🔵 Needs a closer look
Add #job-selection to the remaining .md legacy redirects.
Pull request overview
Renames the “Monorepo CI” integration feature to “Job Selection” while updating related links, anchors, redirects, and assets.
Changes:
- Updates integration documentation, cards, and descriptions.
- Migrates internal links to
#job-selectionwhile preserving legacy anchors. - Renames the workflow example and screenshot asset.
File summaries
| File | Summary |
|---|---|
src/content/docs/merge-queue/scopes/file-patterns.mdx |
Updates Job Selection references. |
src/content/docs/merge-queue/scopes.mdx |
Updates integration links. |
src/content/docs/merge-queue/monorepo.mdx |
Updates Job Selection links. |
src/content/docs/merge-queue/migrate-partitions-to-scopes.mdx |
Updates the integration link. |
src/content/docs/integrations/gha.mdx |
Renames GitHub Actions feature content and screenshot reference. |
src/content/docs/integrations/buildkite.mdx |
Renames Buildkite feature content. |
src/content/docs/integrations.mdx |
Updates integration cards. |
public/_redirects |
Updates legacy redirects; some .md routes still lack the new fragment. |
Review details
Suppressed comments (1)
public/_redirects:96
- The
.mdlegacy routes immediately below these entries (/monorepo-ci.md,/monorepo-ci/github-actions.md, and/monorepo-ci/buildkite.md) still redirect without a fragment, so those/monorepo-ci*URLs land at the top of the integration page while the other variants land at Job Selection. Add#job-selectionto these destinations as well so every legacy route preserves the section target described by this change.
/monorepo-ci /integrations/gha#job-selection 301
/monorepo-ci/ /integrations/gha#job-selection 301
- Files reviewed: 8/9 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
jd
marked this pull request as ready for review
September 16, 2026 12:44
"Monorepo CI" named the topic rather than the feature: it is scopes deciding which CI jobs or Buildkite steps a pull request needs. "Job Selection" says what it does and sits next to Test Selection as its job-level sibling. - Rename the section, intro, feature bullet and frontmatter description on the GitHub Actions and Buildkite integration pages, and the two cards on the integrations index. - Move the anchor to `#job-selection` on every page that links to it (merge queue monorepo guide, scopes, file-pattern scopes, partitions migration) and in the `/monorepo-ci*` redirects. - Keep a hidden `monorepo-ci` anchor above each renamed heading, so links to the old anchor still land on the section instead of the top of the page. A fragment never reaches the server, so a redirect cannot do this. - Rename the example workflow from `Monorepo CI` to `CI`, and the job summary screenshot file to match the new name. Fixes MRGFY-9345 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Change-Id: I699fe8039b79e1d7370f8f9439a6cc20c536b420
jd
force-pushed
the
devs/jd/jd/mrgfy-9345-rename-monorepo-ci-to-job-selection-in-the-github-actions/rename-monorepo-ci-job-selection--699fe803
branch
from
September 16, 2026 13:48
304623c to
8805e54
Compare
Member
Author
Revision history
|
Member
Author
|
Rebased onto main to pick up the build fix from #12859. Main was failing I left Copilot's suggestion about the |
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.
"Monorepo CI" named the topic rather than the feature: it is scopes deciding
which CI jobs or Buildkite steps a pull request needs. "Job Selection" says
what it does and sits next to Test Selection as its job-level sibling.
the GitHub Actions and Buildkite integration pages, and the two cards on
the integrations index.
#job-selectionon every page that links to it(merge queue monorepo guide, scopes, file-pattern scopes, partitions
migration) and in the
/monorepo-ci*redirects.monorepo-cianchor above each renamed heading, so links tothe old anchor still land on the section instead of the top of the page.
A fragment never reaches the server, so a redirect cannot do this.
Monorepo CItoCI, and the jobsummary screenshot file to match the new name.
Fixes MRGFY-9345
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com