-
Notifications
You must be signed in to change notification settings - Fork 369
organization_access_token: Add SANDBOX_
to tokens when in sandbox env
#6058
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📦 Next.js Bundle Analysis for webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 🎉 Global Bundle Size Decreased
DetailsThe global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster. Any third party scripts you have added directly to your app using the If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! |
63af746
to
c8c1d20
Compare
98b752b
to
fff1030
Compare
Does the same for personal access tokens, but those are deprecated and thus no longer being created (but are potentially still in use by customers).
fff1030
to
346613a
Compare
# that. | ||
# The prefix is listed here for later reference. | ||
# | ||
# TOKEN_PREFIX = "polar_pat_" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing comment 👍
LGTM! Edit: we can do the special error message when detecting a sandbox prefix in production in another PR. |
Tested with tokens created inside and outside of sandbox, both on
main
.main
("before this change") works on this branch ✅