Task: Write a clever script to automatically generate distribution-wide changelog
As far as i can tell there's no way to truly automatically capture all changes from all drutopia_*
projects unless we start committing a composer.lock
file. But as long as we take the time to manually update our composer.json
file to reference then-current releases of required drutopia_*
projects, it should be possible to automate the rest:
-
Fetch the Drutopia distribution's composer.json
file for the current tagged release and the next-most-recent tagged release. -
Parse each file for the release (version, such as 8.x-1.0-alpha3
) of alldrutopia_*
projects (drutopia_article
etc.) -
In that projects repository get the commits that occurred between those tags git log 8.x-1.0-alpha3..8.x-1.0-alpha4 --pretty=format:"[%h](https://gitlab.com/drutopia/${i::-5}/commit/%H) %s (%an) "
-
Rewrite issue numbers as links to issues within appropriate projects; that is #12
as[#12](https://gitlab.org/drutopia/drutopia_example/issues/12)
For the current, more manual approach see http://docs.drutopia.org/en/latest/issuing-new-release-of-features-and-distribution.html and https://gitlab.com/drutopia/hackysync for the scripted bits.
Edited by benjamin melançon