Fix repo_token parameter #263
Merged
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
Signed-off-by: Joyce <joycebrum@google.com>
Signed-off-by: Joyce <joycebrum@google.com>
joshlf
approved these changes
Aug 15, 2023
|
Thanks, @joycebrum! |
joshlf
pushed a commit
that referenced
this pull request
Aug 19, 2023
* Fix repo_token mention * remove comment about private repos Signed-off-by: Joyce <joycebrum@google.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.
Hi @joshlf,
I'm suggesting a fix to the scorecard action because the current naming of
repo-tokenis not being recognized.I've changed it to the suggested one: repo_token. That's probably why Branch-Protection is yet as "?"
Additionally I've cleaned some "not related" comments.
Relates to #230