这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@mengxi-ream
Copy link

Description

Shoud use TEAM ID as TURBO_TEAM rather than TEAM URL

Testing Instructions

Test on Github Action

@mengxi-ream mengxi-ream requested review from a team and anthonyshew as code owners August 16, 2025 20:37
@mengxi-ream mengxi-ream requested a review from tknickman August 16, 2025 20:37
@turbo-orchestrator turbo-orchestrator bot added area: docs Improvements or additions to documentation needs: triage labels Aug 16, 2025
@vercel
Copy link
Contributor

vercel bot commented Aug 16, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
examples-basic-web Ready Ready Preview Comment Aug 16, 2025 8:38pm
examples-designsystem-docs Ready Ready Preview Comment Aug 16, 2025 8:38pm
examples-tailwind-web Ready Ready Preview Comment Aug 16, 2025 8:38pm
examples-vite-web Ready Ready Preview Comment Aug 16, 2025 8:38pm

@vercel
Copy link
Contributor

vercel bot commented Aug 16, 2025

@mengxi-ream is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

@anthonyshew
Copy link
Contributor

Hi, this doc is correct. You need to use the team slug for this variable, which is consistent with other documentation (example here). Are you seeing something different?

@mengxi-ream
Copy link
Author

mengxi-ream commented Aug 17, 2025

Hi, this doc is correct. You need to use the team slug for this variable, which is consistent with other documentation (example here). Are you seeing something different?

I used TURBO_TEAM team slug vercel.com/mengxi-ream and can't get the cache in GitHub Action (error is permission related) then replace it as team id, cache worked in GitHub Action

for team slug, should we include Vercel.com or not?

@anthonyshew
Copy link
Contributor

The slug is only mengxi-ream.

@mengxi-ream
Copy link
Author

mengxi-ream

thanks, I'll try

@anthonyshew
Copy link
Contributor

I'll close this up as I've tested this multiple times in the past, and believe the doc to be correct as-is. Thanks for the PR, really appreciate the collaboration!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants