docs: align Vercel secret names and mark legacy workflow as historical - #8
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Member
Author
|
Nice |
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.
Motivation
VERCEL_TOKEN,VERCEL_ORG_ID,VERCEL_PROJECT_ID) and discourage use of older names or committing secrets.Description
.github/Secrets-GitHub.mdto list the exact secret names, where to find their values in the Vercel dashboard, and a shortSetupsection instructing to add them under GitHubSettings → Secrets and variables → Actionsand not to commit secrets..github/workflow.mdwith a clear legacy note pointing to the active workflow at/.github/workflows/ci-cd.yamland list the correct secret names while explicitly stating the old names are not used.Testing
rg -n 'VERCEL_(TOKEN|ORG_ID|PROJECT_ID)' .github/Secrets-GitHub.md .github/workflow.mdand confirmed the new names are present (succeeded).rg -n 'secrets\.VERCEL_(TOKEN|ORG_ID|PROJECT_ID)' .github/workflows/ci-cd.yamland confirmed the workflow readsVERCEL_TOKEN,VERCEL_ORG_ID, andVERCEL_PROJECT_ID(succeeded).git diff --checkandgit status --short --branchto validate whitespace and working tree state (no errors reported).git remote -vreturned no configured remote so repository remote-based operations (pushing, creating PR viagh) could not be performed, and acurlquery to the Vercel API returned403when trying to fetch project metadata, so external verification against Vercel could not be completed.Codex Task