fix(ci): persist-credentials: false on release, agent-restricted, strands-command#2
Merged
Merged
Conversation
…ands-command Defense-in-depth: stop persisting the GITHUB_TOKEN in the git credential store on three workflows that previously left it populated after checkout. - release.yml (prepare-release + publish-npm): add persist-credentials: false and explicit insteadOf step before every git push so push still works without the persisted token. - agent-restricted.yml: add persist-credentials: false; the strands-action already configures its own git credentials via pat_token input. - strands-command.yml: same pattern as agent-restricted. - test-and-build job already had persist-credentials: false and is left unchanged.
Coverage Report
|
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
1 participant
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.
Summary