docs: Improve instructions for patch release #2720
Conversation
|
|
||
| **Release-please method** Make sure the name of your branch begins `release/` so | ||
| the release-please workflow automatically runs on it. This will create the draft | ||
| PR with ChangeLog updates. When approved, merge, and this will trigger release-please to actually make the release. |
There was a problem hiding this comment.
This is only 90% what I did. I created the branch without the release/ prefix so had to manually run release-please. Then I created the same branch with that prefix, and I think #2718 was automatically created as expected...but the release PR that I merged was the first one, with me manually changing the PR target branch.
So I'm 97% sure this is correct / all you need to do, but not quite the final 3%....
acl-cqc
changed the title
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2720 +/- ##
=======================================
Coverage 83.55% 83.55%
=======================================
Files 266 266
Lines 51761 51761
Branches 47180 47180
=======================================
Hits 43251 43251
Misses 6132 6132
Partials 2378 2378
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
No description provided.