I should have the PR description include a new heading, ## Release notes. It should be initially seeded with the generated notes from the draft release's creation, and then when you update the PR, it should update the draft. (To prevent infinite loops, I should probably have it be only one-way; but maybe have the PR's validation include a check that they're in sync, or even just do it?)
Along with the recently commited #296, this means I don't even really need to look at the draft PR at all. Everything I need is in the PR, which means I'm less likely to accidentally publish the release manually.
This would also benefit from #297.
I should have the PR description include a new heading,
## Release notes. It should be initially seeded with the generated notes from the draft release's creation, and then when you update the PR, it should update the draft. (To prevent infinite loops, I should probably have it be only one-way; but maybe have the PR's validation include a check that they're in sync, or even just do it?)Along with the recently commited #296, this means I don't even really need to look at the draft PR at all. Everything I need is in the PR, which means I'm less likely to accidentally publish the release manually.
This would also benefit from #297.