The versioning problem specified in softwareengineering.stackexchangearchive link on how to handle multiple simultaneous pull requests that all increment the versions of a package.
It was suggested that the user submitting the PR should not be responsible for incrementing the version, which I agree with. Also, having the user be responsible for incrementing the version makes the order of merging the changes very brittle due to the version change becoming obsolete if another PR is merged first.
The user should have an ability to specify the type of version increment by specifying something like patch, feature, breaking, or paradigm in the git commit or a changes attributes file.
Is there a ci tool that can automatically update the versions in the package.yaml, cabal, and ChangeLog.md files?
The versioning problem specified in softwareengineering.stackexchange archive link on how to handle multiple simultaneous pull requests that all increment the versions of a package.
It was suggested that the user submitting the PR should not be responsible for incrementing the version, which I agree with. Also, having the user be responsible for incrementing the version makes the order of merging the changes very brittle due to the version change becoming obsolete if another PR is merged first.
The user should have an ability to specify the type of version increment by specifying something like patch, feature, breaking, or paradigm in the git commit or a changes attributes file.
Is there a ci tool that can automatically update the versions in the package.yaml, cabal, and ChangeLog.md files?