You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The config docs - and example config given in the Vercel docs - demonstrate adding the $GITHUB_TOKEN env var to globalDependencies - which I interpret as quite strongly implying this is something we likely want to do(!)
If I understand correctly, this will effectively give every user and CI environment its own isolated remote cache (based on different Github tokens). However the Remote Caching docs describe the feature as "a way to take advantage of the computational work done by your teammates or your CI" - and isolating the cache per-user would seem to limit the benefits of Remote caching for local use (albeit helping CI).
So - if/when is it recommended to add $GITHUB_TOKEN to the global dependencies?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Enjoying getting started!
The config docs - and example config given in the Vercel docs - demonstrate adding the
$GITHUB_TOKEN
env var toglobalDependencies
- which I interpret as quite strongly implying this is something we likely want to do(!)If I understand correctly, this will effectively give every user and CI environment its own isolated remote cache (based on different Github tokens). However the Remote Caching docs describe the feature as "a way to take advantage of the computational work done by your teammates or your CI" - and isolating the cache per-user would seem to limit the benefits of Remote caching for local use (albeit helping CI).
So - if/when is it recommended to add
$GITHUB_TOKEN
to the global dependencies?Perhaps this could then be clarified in the docs.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions