I’ve noticed that most (if not all) of the community created steps have empty change lists in CLI changelog. E.g. in the latest one: Monthly release of Bitrise CLI tools and summary of updates (Jun, 2017) - CLI v1.6.2 [image] Monthly release of Bitrise CLI tools and summary of updates (Jun, 2017)…

Hi @koral , the step changelogs are semi auto generated. We have a tool which collects the changes from the steps github release pages (then we review/reformat the generated changelog).

OK, is that documented somewhere? Such information should be written in https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md perhaps.

Not documented as it’s not a final solution - not used anywhere else, only in our monthly updates, where we collect the changelogs with a custom script. The CLI itself does not require this nor does it handle it in any way. To be honest we’re not sure this should be the official solution, given tha…

Any time :wink: BTW if you have an idea for a pure git based solution, without depending on git hosting specific features just let us know! For now we’re thinking about building this into the CLI, as part of a bitrise :step share plugin command which would replace the current sharing procedure. It…

[image] viktorbenei: pure git based solution, without depending on git hosting specific features Collecting commit messages between current and previous version tag. That may be one of the sources which may be chosen apart from [quote=“viktorbenei, post:6, topic:2018”] release notes, includi…

[image] koral: Collecting commit messages between current and previous version tag. That’s a good idea for an option, but wouldn’t make that the default - from our experience this would create insanely noise release notes for most steps. But as an option in the step share plugin, definitely!

Yeah, there is probably no good universal default because each author may prefer different solution. Maybe CLI can remember that choice for given step id locally and default to previously selected one.

[image] koral: Maybe CLI can remember that choice for given step id locally and default to previously selected one. Definitely a great idea! :wink:

Empty community-created step changelogs

Development Step Dev

viktorbenei June 14, 2017, 2:03pm 7

Planned to be part of Step create plugin - quickly generate a new step

Topic		Replies	Views
Generate-changelog step generates empty CHANGELOG.md Tooling Issues step	0	799	October 9, 2019
Generate Changelog v0.10.2 Changelog step-update	0	110	April 10, 2024
Automatically generate release notes for github release Steps step , github , release , release-notes	0	1190	November 15, 2021
Monthly release of Bitrise CLI tools and summary of updates (Feb, 2017) Changelog bitrise-cli , bitrise-tools , announcements	0	1194	February 13, 2017
Possible to get Release Notes into the Hockey App step? Tooling Issues step	1	1764	April 3, 2018

Empty community-created step changelogs

Related topics