-
Notifications
You must be signed in to change notification settings - Fork 512
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
🌱 Logging a warning if readGitHubTokens finds several values which clash. #4483
🌱 Logging a warning if readGitHubTokens finds several values which clash. #4483
Conversation
Signed-off-by: Simon Heidrich <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4483 +/- ##
==========================================
+ Coverage 66.80% 68.46% +1.65%
==========================================
Files 230 246 +16
Lines 16602 18444 +1842
==========================================
+ Hits 11091 12627 +1536
- Misses 4808 4991 +183
- Partials 703 826 +123 |
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.
Generally looks good. Left a few comments, and make sure to run make check-linter
.
Signed-off-by: Simon Heidrich <[email protected]>
Signed-off-by: Simon Heidrich <[email protected]>
Signed-off-by: Simon Heidrich <[email protected]>
…dered the line too long. Signed-off-by: Simon Heidrich <[email protected]>
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.
Thank you!
What kind of change does this PR introduce?
Print a warning if several GitHub Access Tokens with different values are found.
What is the current behavior?
Scorecard ignores any GitHub PAT environment variables after the first one it finds.
What is the new behavior (if this is a feature change)?**
Scorecards checks all possible PAT env vars and prints a warning if their values differ. It still uses the first one it finds, such that the behaviour is non-breaking.
Which issue(s) this PR fixes
Fixes #4475
Special notes for your reviewer
The local tests failed already for a clean checkout of the main branch. I am hoping for the CI to sucessfully run them for me.
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)