🐛 Branch-Protection: use debug message when unsure if PRs are required #3917
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
bug fix
What is the current behavior?
When run with a non-admin token, if we cant tell if PRs are required, we throw a warning.
What is the new behavior (if this is a feature change)?**
Since requiring PRs is listed as potentially admin only data, not having the data is now DEBUG, not WARN.
scorecard/docs/checks.md
Lines 113 to 115 in 90a3708
Which issue(s) this PR fixes
NONE
Special notes for your reviewer
I got rid of the
switch
statement since the function is only called by 3 probes, and all of them want that behavior.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.)