ci: Set author and pin SHA in vuln-scan workflow PR #2153
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
| with: | ||
| token: "${{ secrets.GITHUB_TOKEN }}" | ||
| author: jupyterhub vuln-scan bot <[email protected]> |
There was a problem hiding this comment.
I think this LGTM, I wonder what the outcome will be visually in GitHub's UI of not setting the committer and leaving it as the default of GitHub <[email protected]>.
3 tasks
consideRatio
changed the title
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.
Follow-up from #2151 (comment)
The committer defaults to
GitHub <[email protected]>which is fine.