-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci(release): allow botanik to sign release commits #522
Conversation
WalkthroughThe update to the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- .github/workflows/release.yml (1 hunks)
Additional comments: 1
.github/workflows/release.yml (1)
- 32-40: The addition of the GPG key import step using
crazy-max/ghaction-import-gpg
is correctly placed within the workflow and is configured to set global git configurations for signing commits. Ensure that the secrets used (OKP4_BOT_GPG_PRIVATE_KEY
andOKP4_BOT_GPG_PASSPHRASE
) are properly set in the repository's secrets.
Make botanik sign release commits
Summary by CodeRabbit