fix broken links in versioned docs for 71-66 releases#3661
Merged
Conversation
✅ Deploy Preview for react-native ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
cortinico
approved these changes
Mar 31, 2023
cortinico
left a comment
cortinico
left a comment
Contributor
There was a problem hiding this comment.
Same as the other pr, I've skimmed through the diff and it looks good to me 👍
If there is any meaningful change to review please let me know
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
3 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.
Why
It's a continuation of efforts to get rid of broken links started in #3660
How
This PR updates all of the
main/masterlinks used in versioned documentation for releases from 0.66 to 0.71, with a links pointing to the specific release branches.It would be nice to establish a pattern, a do the links replacement after cutting a new docs version.