You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
Since breaking changes are inevitable, I think introducing a changelog would be a good idea.
I propose to follow the format described on keepachangelog.com. Usually, it's not a huge maintenance burden: contributors guide can be updated to require updating the changelog with each PR (especially if the change is breaking).
The text was updated successfully, but these errors were encountered:
We are currently tracking changes on the Releases page, which is reasonably easy to extract from the git logs. However, I would generally not approve of any "better" change tracking mechanism that we can't enforce through a CI check.
If you have any suggestions, then we could probably have a conversation on setting up a policy to make this easier.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since breaking changes are inevitable, I think introducing a changelog would be a good idea.
I propose to follow the format described on keepachangelog.com. Usually, it's not a huge maintenance burden: contributors guide can be updated to require updating the changelog with each PR (especially if the change is breaking).
The text was updated successfully, but these errors were encountered: