chore: add CHANGELOG file for app #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In other apps there is a habit to keep an explicit changelog which, among other things, documents the steps to follow to deploy a release. In the past I found this rather handy, especially if multiple people contributed to a single release (and/or too much time has passed since deploying to DEV for my memory to recall what I did at the time.)
I would propose we also do this for this app. Although, it will probably be less crucial here due to the POC-nature of the app, with possibly few (if any) releases. The idea would be that
In this PR I added a small example of what an entry would be for the functionality added in another PR. Some examples of more extensive changelogs can be, for example, found in Digitaal Loket or OrganisatiePortaal.