Fix outdated README links that redirect (#208)#209
Open
shujanislam wants to merge 1 commit intovercel:mainfrom
Open
Fix outdated README links that redirect (#208)#209shujanislam wants to merge 1 commit intovercel:mainfrom
shujanislam wants to merge 1 commit intovercel:mainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates outdated README links to their canonical destinations, avoiding unnecessary redirects. The changes update Vercel documentation URLs from the old vercel.com/docs format to the new docs.vercel.com format, and updates the community link from vercel.community to community.vercel.com.
Changes:
- Updated Vercel Community link from vercel.community to community.vercel.com
- Updated Vercel REST API documentation link to use the new docs.vercel.com domain
- Updated "Creating an Access Token" documentation link to use the new docs.vercel.com domain
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## Access Tokens | ||
|
|
||
| You need to pass a valid access token to be able to use any resource or operation. Refer to [Creating an Access Token](https://vercel.com/docs/rest-api#creating-an-access-token) to learn how to create one. Make sure that you create a token with the correct Vercel [scope](https://vercel.com/docs/dashboard-features#scope-selector). | ||
| You need to pass a valid access token to be able to use any resource or operation. Refer to [Creating an Access Token](https://docs.vercel.com/docs/rest-api/reference/welcome#creating-an-access-token) to learn how to create one. Make sure that you create a token with the correct Vercel [scope](https://vercel.com/docs/dashboard-features#scope-selector). |
There was a problem hiding this comment.
The link to the Vercel scope documentation still uses the old format https://vercel.com/docs/dashboard-features#scope-selector. For consistency with the other updates in this PR and to avoid redirects, this link should also be updated to use the new documentation URL format (starting with https://docs.vercel.com/).
Suggested change
| You need to pass a valid access token to be able to use any resource or operation. Refer to [Creating an Access Token](https://docs.vercel.com/docs/rest-api/reference/welcome#creating-an-access-token) to learn how to create one. Make sure that you create a token with the correct Vercel [scope](https://vercel.com/docs/dashboard-features#scope-selector). | |
| You need to pass a valid access token to be able to use any resource or operation. Refer to [Creating an Access Token](https://docs.vercel.com/docs/rest-api/reference/welcome#creating-an-access-token) to learn how to create one. Make sure that you create a token with the correct Vercel [scope](https://docs.vercel.com/docs/dashboard-features#scope-selector). |
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
1 participant
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.
Updates README links that were pointing to outdated URLs and relying on redirects. The links now point directly to their canonical destinations, avoiding unnecessary redirect hops and helping future-proof the documentation.
Documentation-only change
No behavior or API changes