馃摉 specify that classic personal access tokens are needed #2565
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmaraya
temporarily deployed
to
integration-test
GitHub Actions
Inactive
|
Integration tests success for |
laurentsimon
approved these changes
Dec 22, 2022
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 |
2 tasks
|
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>
naveensrinivasan
had a problem deploying
to
integration-test
GitHub Actions
Failure
naveensrinivasan
temporarily deployed
to
integration-test
GitHub Actions
Inactive
spencerschrock
approved these changes
Jan 5, 2023
|
Integration tests success for |
raghavkaul
pushed a commit
to raghavkaul/scorecard
that referenced
this pull request
Feb 9, 2023
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>
raghavkaul
pushed a commit
to raghavkaul/scorecard
that referenced
this pull request
Apr 4, 2023
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>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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.)