Allow the persist-credentials for the release operation#215
Conversation
To run git push, the credential is needed.
WalkthroughThe release workflow configuration was updated to change the repository checkout step in the "tagpr" job. Specifically, the Changes
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Pull Request Overview
This PR enables the release operation to use persisted credentials required for performing a git push.
- Changed the persist-credentials value from false to true in the checkout step to allow credential persistence.
Comments suppressed due to low confidence (1)
.github/workflows/release.yml:26
- Enabling 'persist-credentials: true' is necessary for the release operation, but please review if this change exposes credentials to unintended reuse in later steps.
persist-credentials: true
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
.github/workflows/release.yml (1)
25-27: Consider fetching full history if the TagPR action requires itBy default,
actions/checkoutusesfetch-depth: 1, which fetches only the latest commit. If the TagPR action needs the complete commit history (for changelog generation or determining release versions), you may want to addfetch-depth: 0:with: - persist-credentials: true + persist-credentials: true + fetch-depth: 0
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.github/workflows/release.yml(1 hunks)
🔇 Additional comments (1)
.github/workflows/release.yml (1)
25-27: Enable persisting GitHub credentials for the tagpr checkoutSetting
persist-credentials: trueensures that theGITHUB_TOKENis written to the local Git configuration, allowing the TagPR action to performgit push(e.g., to push tags) without authentication errors. This directly addresses the PR objective.
close #
✏️ Description
A credential is needed to run git push.