ci: Do not persist credentials#11
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR enhances security in the Go dependency update workflow by switching from SSH key authentication to token-based authentication and disabling credential persistence.
Changes:
- Replaced
ssh-keywithtokenfor repository checkout authentication - Added
persist-credentials: falseto prevent credentials from being stored in git config
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
HomayoonAlimohammadi
approved these changes
Jan 30, 2026
ktsakalozos-canonical
pushed a commit
that referenced
this pull request
May 28, 2026
This file contains hidden or 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
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.
actions/checkoutis setting up an authorization header that persists. The create-pull-request action then tries to add its own HTTPS authorization header using the BOT_TOKEN secret. GitHub receives two headers and rejects the request with a 400 Bad Request.This PR replaced
ssh-keywithtokenfor repository checkout authentication