[GH-ISSUE #510] Add standardized changelog to track release changes #177

New issue

Closed

opened 2026-03-02 04:12:36 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 04:12:36 +03:00

Owner

Originally created by @m4rii0 on GitHub (Feb 12, 2026).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/510

Summary

Hi team 👋

It would be really helpful to have an easy way to see what changed between releases. At the moment, the GitHub releases do not include detailed notes, which makes it hard for users and contributors to quickly understand what is new, fixed, or modified.

Proposal

Would it be possible to add a CHANGELOG.md file at the root of the repository following the Keep a Changelog 1.1.0 standard?
https://keepachangelog.com/en/1.1.0/

Using this format would provide:

A clear and consistent history of changes
Structured sections such as Added, Changed, Fixed, Deprecated, Removed, Security
Version entries aligned with Semantic Versioning
An Unreleased section for upcoming changes

Why This Helps

Makes it much easier to track differences between versions
Improves transparency for users
Reduces questions about what changed in each release
Helps contributors understand project evolution

Thanks for considering this 🙂

Originally created by @m4rii0 on GitHub (Feb 12, 2026). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/510 ## Summary Hi team 👋 It would be really helpful to have an easy way to see what changed between releases. At the moment, the GitHub releases do not include detailed notes, which makes it hard for users and contributors to quickly understand what is new, fixed, or modified. ## Proposal Would it be possible to add a `CHANGELOG.md` file at the root of the repository following the Keep a Changelog 1.1.0 standard? [https://keepachangelog.com/en/1.1.0/](https://keepachangelog.com/en/1.1.0/) Using this format would provide: * A clear and consistent history of changes * Structured sections such as Added, Changed, Fixed, Deprecated, Removed, Security * Version entries aligned with Semantic Versioning * An Unreleased section for upcoming changes ## Why This Helps * Makes it much easier to track differences between versions * Improves transparency for users * Reduces questions about what changed in each release * Helps contributors understand project evolution Thanks for considering this 🙂