-
Notifications
You must be signed in to change notification settings - Fork 474
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
📖 specify that classic personal access tokens are needed #2565
Conversation
Integration tests success for |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2565 +/- ##
=======================================
Coverage 40.03% 40.03%
=======================================
Files 122 122
Lines 9865 9865
=======================================
Hits 3949 3949
Misses 5635 5635
Partials 281 281 |
note: this PR can't be merged due to some CI config problems. see #2508 (comment) for details. trying to get this cleared up |
Stale pull request message |
Clarified that classic personal access tokens, not fine-grained ones, are needed for scorecard to work. Signed-off-by: Mike Maraya <mmaraya@users.noreply.github.com>
Integration tests success for |
Clarified that classic personal access tokens, not fine-grained ones, are needed for scorecard to work. Signed-off-by: Mike Maraya <mmaraya@users.noreply.github.com> Signed-off-by: Mike Maraya <mmaraya@users.noreply.github.com>
Clarified that classic personal access tokens, not fine-grained ones, are needed for scorecard to work. Signed-off-by: Mike Maraya <mmaraya@users.noreply.github.com> Signed-off-by: Mike Maraya <mmaraya@users.noreply.github.com>
Signed-off-by: Mike Maraya mmaraya@users.noreply.github.com
What kind of change does this PR introduce?
Doc update to clarify that classic, not fine-grained, personal access tokens are required for the scorecard CLI to work
(Is it a bug fix, feature, docs update, something else?) docs update
What is the current behavior? documentation currently links to the creation of a fine-grained access token, which produces this error:
What is the new behavior (if this is a feature change)?** n/a, doc change only
Which issue(s) this PR fixes
NONE
Special notes for your reviewer
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.)