-
Notifications
You must be signed in to change notification settings - Fork 429
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
chore(ci): use environment variables, not secrets, for non-sensitive vars #7598
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
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.
👍 looks good
Component Testing Report Updated Oct 5, 2024 3:00 PM (UTC) ✅ All Tests Passed -- expand for details
|
⚡️ Editor Performance ReportUpdated Sat, 05 Oct 2024 15:11:06 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
…vars (#7598) ### Description I don't think there's any reason to hide variables such as dataset and project IDs. It makes it harder to debug issues and read logs, as any value in these secrets will be scrubbed from logs as `****`. In particular, we use `test` as a dataset name 😅 ### What to review - CI configs still looks right - [Environment variables](https://github.com/sanity-io/sanity/settings/variables/actions) are in place to take the place of the secrets ### Testing Letting the CI workflows run should be enough ### Notes for release None
### Description This changes some remaining references to secrets in the e2e workflow after #7598 moved them to env vars. ### What to review Did I miss any? ### Testing CI passes, I guess? ### Notes for release n/a
Description
I don't think there's any reason to hide variables such as dataset and project IDs. It makes it harder to debug issues and read logs, as any value in these secrets will be scrubbed from logs as
****
. In particular, we usetest
as a dataset name 😅What to review
Testing
Letting the CI workflows run should be enough
Notes for release
None