scrub deploy IDs and team scope from public workflow - #167
Merged
Conversation
Flotapponnier
added a commit
that referenced
this pull request
May 29, 2026
scrub deploy IDs and team scope from public workflow
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.
Removes from the public repo:
staging-deploy.ymldocumenting the Vercel team workaround + the actualteam_…andprj_…IDs (anyone reading the workflow had a free blueprint of our Vercel setup).--scope=mobula-labsin the alias step — now pulled fromVERCEL_ORG_IDsecret.vercel alias --scope=accepts a team ID as well as a slug, so no new secret needed.CI side: no secret added, only re-routing an existing one. Staging deploy should keep working.
Note: the IDs are still in git history. They're identifiers (not credentials), so the risk is just reconnaissance — anyone who finds them would still need a valid
VERCEL_TOKENto do anything. Force-purging history would invalidate every open PR / fork hash, not worth it for ID-level info.