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
Regional date formats vary throughout the world and it's often difficult to find a human-friendly date format that feels intuitive to everyone. The advantage of dates formatted like 2017-07-17 is that they follow the order of largest to smallest units: year, month, and day.
maybe it would be better to switch to YYYY-MM-DD ?
The text was updated successfully, but these errors were encountered:
I'd like to propose that Pygls starts using an automatic CHANGELOG generator, such as https://github.com/orhun/git-cliff. And that we require Conventional Commits messages. The CHANGELOG file doesn't have to be auto-populated in CI, although I would like to try that at first. More than anything I would just like it to be populated by a standard tool and we could edit it after the auto-population.
Recent entries are in D/MM/YYYY format:
pygls/CHANGELOG.md
Line 13 in 24fe1f0
Older entries were in MM/DD/YYYY format
pygls/CHANGELOG.md
Line 306 in 24fe1f0
From CHANGELOG.md:
pygls/CHANGELOG.md
Line 5 in 24fe1f0
Keep a Changelog recommends YYYY-MM-DD format.
maybe it would be better to switch to YYYY-MM-DD ?
The text was updated successfully, but these errors were encountered: