Skip to content

Reorder workflow to update changelogs first #88

@mcmire

Description

@mcmire

Currently, the workflow of this tool is cumbersome. As soon as the tool is run, it will first generate a release spec, which essentially asks the user to choose the next version of the packages changed. However, to do this, the user must first review the changes that have taken place to those packages. This can be quite painful to do, and it repeats work that this tool does already.

Instead, this tool should first create a new branch and add changelog entries to the appropriate changelogs, filing them under the "Unreleased" header, and then generate the release spec. The user can then review the changelog entries, following the referenced pull requests as necessary, and use this information to complete the release spec. When re-run, the tool would then move the entries from the Unreleased section to new sections corresponding to the determined versions.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions