Skip to content
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

Update token used for scorecard #134

Merged

Conversation

mhutchinson
Copy link
Contributor

This was previously using a github secret that was per-repo. I've switched it over to an org-level secret, which should allow us to avoid copying and pasting the secret around a number of times. Added a note that we should switch over to branch protection rulesets instead, which should mean that this read permission isn't needed at all.

Motivation is that the original token is expiring within the week.

This was previously using a github secret that was per-repo. I've switched it over to an org-level secret, which should allow us to avoid copying and pasting the secret around a number of times. Added a note that we should switch over to branch protection rulesets instead, which should mean that this read permission isn't needed at all.

Motivation is that the original token is expiring within the week.
@mhutchinson mhutchinson requested a review from a team as a code owner August 7, 2024 08:20
@mhutchinson mhutchinson requested a review from phbnf August 7, 2024 08:20
@mhutchinson mhutchinson merged commit 2af592e into transparency-dev:main Aug 7, 2024
10 checks passed
@mhutchinson mhutchinson deleted the scorecard-updateToken branch August 7, 2024 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants