ci: match release automation to desired behavioral workflow#739
Conversation
📝 WalkthroughWalkthroughThe pull request removes the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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. Comment |
7b61bdd to
097d22d
Compare
097d22d to
7d3cf85
Compare
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
Tested against my local branch with |
Description
Drop the changelog commit during the release creation process, don't push tags automatically, & publish the release as a draft. Because of this, a backport from main to develop is no longer required.
This change also means that a commit hitting main isn't an AUTOMATIC release - a human still has to go to the releases page and hit "publish".
Changes
gitchangelogbackportjobSummary by CodeRabbit