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
The current CHANGELOG-TEMPLATE.md file is empty and lacks any entries. To improve project documentation and user awareness of changes, I suggest we start populating the changelog with past releases and updates.
Moreover, having a standardized format for documenting changes will help maintain consistency and clarity. Could we establish guidelines for contributors on how to fill out this template?
The text was updated successfully, but these errors were encountered:
I understand the reasoning behind deleting the changelog template, especially if it hasn't been used. However, I believe having a changelog could still be beneficial for future reference and for new contributors. If the team agrees, perhaps we can consider establishing guidelines on its use before deciding to remove it.
We already have a history of changes inside CHANGELOG.md. The changelog template is for us to copy and edit for CHANGELOG.md when we are making a release.
The current CHANGELOG-TEMPLATE.md file is empty and lacks any entries. To improve project documentation and user awareness of changes, I suggest we start populating the changelog with past releases and updates.
Moreover, having a standardized format for documenting changes will help maintain consistency and clarity. Could we establish guidelines for contributors on how to fill out this template?
The text was updated successfully, but these errors were encountered: