Currently the person who is merging the PR that prompts a new release has to write a changelog with all the changes included in that PR (even if they are not theirs), with the name $(10000 + buildNumber).txt.
Ideally, we would like each person who makes a change to add a corresponding changelog entry. Since we only want a single changelog with all the things included in a release, they shouldn't each create a separate file with the corresponding version - but rather, we could have a default.txt file in which we progressively add changelog entries. This works with the fastlane tool (see docs).
When a release is ready, the default.txt file should be renamed to $(10000 + buildNumber).txt before release.
To achieve this, we need to update documentation and the automated checks in the linter.
Currently the person who is merging the PR that prompts a new release has to write a changelog with all the changes included in that PR (even if they are not theirs), with the name
$(10000 + buildNumber).txt.Ideally, we would like each person who makes a change to add a corresponding changelog entry. Since we only want a single changelog with all the things included in a release, they shouldn't each create a separate file with the corresponding version - but rather, we could have a default.txt file in which we progressively add changelog entries. This works with the fastlane tool (see docs).
When a release is ready, the default.txt file should be renamed to
$(10000 + buildNumber).txtbefore release.To achieve this, we need to update documentation and the automated checks in the linter.