Move multiple origins page into source maps troubleshooting page #5786
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Lms24
approved these changes
Nov 15, 2022
imatwawana
reviewed
Nov 15, 2022
Co-authored-by: Isabel <[email protected]>
lforst
deleted the
lforst-move-multiple-origins-into-troubleshooting-section
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 PR is part of a bigger restructuring #5784 of the source maps upload docs.
Currently, the "Multiple Origins" page lives under the "Uploading Source Maps" section which is not really fitting and in conflict with future pages we want to have under the "Uploading Source Maps" section.
This PR moves that page into the troubleshooting page as a subheading, as it is more of an edge case for users. Additionally, this PR adds a redirect in the
vercel.jsonthat points from the old page to the new heading on the troubleshooting page