Open
Conversation
Collaborator
Author
|
@mkaply do you want to give this a try with npm run build && npm run preview |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description:
First proper try at keeping a relevant changelog for admins. There's a bit of manual work at the moment, but it's high importance for surfacing changes to readers and will be good to iterate on.
I was considering a few different ways of tracking changes, using git tagging, keeping branches per release train etc, for now, the simplest approach is to prefix changelog entries in a single CHANGELOG.md. We may want to revisit in future.
Motivation:
Keep changes visible and improve traceability.
Related issues and pull requests: