Repository navigation
docs(integrations): Consolidate code mappings onto one page - #20037
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
There was a problem hiding this comment.
🔵 Needs a closer look
The rollout-dependent workflow needs human validation, and three planned UI screenshots remain outstanding.
0 open findings
What changed in this PR
Consolidates code mapping documentation around the new project and repository settings workflow.
Changes:
- Adds a canonical setup guide covering prefixes, editing, automatic mappings, and bulk uploads.
- Replaces duplicated provider walkthroughs with links and updates field names and cross-references.
- Removes obsolete setup content and reuses a central native stack trace screenshot.
| File | Description |
|---|---|
| includes/common-imgs/code-mappings-configure-modal.md | Removes obsolete modal include. |
| docs/product/issues/suspect-commits/index.mdx | Links canonical setup; removes stale demo. |
| docs/product/issues/ownership-rules/index.mdx | Updates code mapping links. |
| docs/product/issues/issue-details/performance-issues/web-vitals/index.mdx | Updates prerequisite link. |
| docs/platforms/java/common/source-context/index.mdx | Updates field names and setup link. |
| docs/platforms/godot/configuration/source-context.mdx | Updates prefix terminology and setup link. |
| docs/platforms/go/common/troubleshooting.mdx | Links canonical mapping guidance. |
| docs/platforms/go/common/source-context/index.mdx | Links canonical setup. |
| docs/integrations/source-code-mgmt/source-context/index.mdx | Updates setup reference. |
| docs/integrations/source-code-mgmt/perforce/index.mdx | Consolidates setup; preserves depot-specific guidance. |
| docs/integrations/source-code-mgmt/index.mdx | Lists Code Mappings under Features. |
| docs/integrations/source-code-mgmt/gitlab/index.mdx | Replaces duplicated setup with canonical link. |
| docs/integrations/source-code-mgmt/github/index.mdx | Consolidates setup and updates prerequisite link. |
| docs/integrations/source-code-mgmt/cursor-origin/index.mdx | Consolidates setup and updates field names. |
| docs/integrations/source-code-mgmt/code-mappings/index.mdx | Adds canonical configuration guide. |
| docs/integrations/source-code-mgmt/code-mappings/img/code-mappings-stacktrace-native.png | Provides shared native stack trace example. |
| docs/integrations/source-code-mgmt/bitbucket/index.mdx | Replaces duplicated setup with canonical link. |
| docs/integrations/source-code-mgmt/azure-devops/index.mdx | Replaces duplicated setup with canonical link. |
| docs/cli/code-mappings.mdx | Updates web UI setup link. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Code mapping setup is moving out of the integration configuration tab and into project and repository settings. The setup walkthrough was copied under every SCM integration and under Suspect Commits, each copy describing the old Settings > Integrations > Configure > Code Mappings tab and the old Stack Trace Root / Source Code Root field names. Add a canonical page at /integrations/source-code-mgmt/code-mappings/ covering path configuration only, and reduce the duplicated sections to a short description plus a link. Provider install, commit tracking, and resolve-via-commit stay on the integration pages. - Add the canonical page: what code mappings do, both new entry points, path fields, how to pick prefixes, editing, automatic mappings, bulk upload, and platform exceptions - Replace the duplicated setup on the GitHub, GitLab, Bitbucket, Azure DevOps, Perforce, and Cursor Origin pages, keeping each provider's Stack Trace Linking anchor and provider-specific behavior - Trim Suspect Commits to suspect-commit behavior and drop the stale Arcade demo - Rename Stack Trace Root to Stack trace prefix and Source Code Root to Repository prefix across the Java, Godot, and Cursor Origin pages (the CLI JSON keys stackRoot and sourceRoot are unchanged) - Repoint code mapping links on SCM Source Context, Ownership Rules, Web Vitals, Go source context and troubleshooting, and CLI - List the new page under Features on the Source Code Management index - Delete the stale configure-modal include and the five duplicated copies of the native stack trace screenshot Screenshots of the new UI are still to come; three placeholders are marked in the canonical page. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Tighten the voice on the canonical page: use "repo" over "repository" in prose, lead the feature list with what each feature does, and even out the phrasing in the setup and edit sections. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Replace the three screenshot placeholders on the canonical page with captures of the new UI: the Connected Repositories panel in project settings, the organization Repositories page, and the connect modal. Also describe the modal's Example preview, which the connect modal screenshot shows but the page didn't explain. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
8d05b0d to
26a758a
Compare
|
The plan checks page loads on the new setup page. It also checks GitHub and GitLab page loads, 404s, and error events. An issue escalates when the new page stays unused or those 404s rise. Monitoring in Services: Mention PlanWhat changedRequests to
RiskA missing new page returns a 404 and blocks setup. A broken GitHub or GitLab page drops those page loads and raises 404s. A broken suspect commits page hides the remaining guidance. New screenshots can fail to render on the setup page. Intended effectThe new setup page must gain page loads after deploy. GitHub and GitLab pages still loading while this counter stays at the pre-deploy noise means The last 24h already shows 4 page loads. The last 7d shows 8. That traffic may be preview noise. Confirmed means a rise above that noise as provider pages link here.
Regression watchBroken MDX on this path 404s under Sunday 24h page loads were lower than Monday. Stay inside the measured 24h band. A drop to zero on GitHub or GitLab is a regression even inside a quiet window.
Not observablePageload latency and HTTP 5xx traces timed out. Image file 404s do not increment Get Slack DMs about this change: cursor.com/automations/rollouts |
|
Verified in
|
DESCRIBE YOUR PR
Code mapping setup is moving out of the integration configuration tab and into project and repository settings. This PR consolidates the docs to match.
Today the setup walkthrough is copied under every SCM integration and again under Suspect Commits. Every copy describes the old Settings > Integrations > Configure > Code Mappings tab and the old Stack Trace Root / Source Code Root field names. This replaces those copies with one canonical page and short provider-specific links.
/integrations/source-code-mgmt/code-mappings/covering what code mappings do, both new entry points, the path fields, how to pick prefixes, editing, automatic mappings, bulk upload, and platform exceptions#stack-trace-linkinganchor and provider-specific behaviorstackRootandsourceRootare unchanged)No redirects are needed: the old content lived at anchors on pages that still exist, and every one of those anchors is preserved.
Note for reviewers
Per the spec, this is written as though
organizations:code-mappings-refactoris fully rolled out and the integration Code Mappings tab is gone. The Vercel preview will describe UI that may not match production yet.IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
🤖 Generated with Claude Code