Open gniftygnome opened 7 months ago
ideally it would be optional
100%, it would be opt-in and you could always use your own soltuion, in the same way you can now.
Ferry requires the user tell it the last tag, which means to run the workflow we have to go look that up first. However, it makes the behavior a bit more flexible and is not dependent on GH actions.
I wonder if the solution would be to have multiple ways to supply the last commit, either manually, from the last succesfull GHA run (same as the fabric scripts), or the last tag on the branch?
The API could be something along the following lines?
publishMods {
changelog = githubActions {
workflow = "release.yml"
}
changelog = git {
from = "v1.0.0" // Tag name
}
}
The API could be something along the following lines?
I like this.
From #25:
From #28:
So, here's a new issue!
Personally, I'm fine with the current situation, since Ferry already has changelog generation we like. If changelog generation gets added to MPP, ideally it would be optional. A couple of differences I think I see:
-
which allows using*
to generate programmer-facing log lines that don't go into the user-facing publications.