keep-a-changelog
keep-a-changelog copied to clipboard
olivierlacan
If you build software, keep a changelog.
Bumps [middleman-syntax](https://github.com/middleman/middleman-syntax) from 3.2.0 to 3.3.0. Changelog Sourced from middleman-syntax's changelog. Fixed HAML :code filter to remove trailing blank lines Commits See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
The English website https://keepachangelog.com/en is redirected to the website of the latest version (v1.1.0) https://keepachangelog.com/en/1.1.0/ However, v1.1.0 of Nederlands translation, for example, is already available https://github.com/olivierlacan/keep-a-changelog/commit/0e74dd2491b8388a69b412c97887f329ebba2292 but, unlike the English...
I'm currently using [parse-changelog](https://github.com/taiki-e/parse-changelog) to parse my changelogs for releases, and it's working quite well. It's also written in Rust, so it's all statically linked and users don't have to...
I maintain 10+ open source projects and I regularly forget to add the github version comparison URL at the bottom of the file. In my projects I moved the URL...
My team and I are "_keep[ing] a changelog_" according to this standard for years now. For our needs we have, though, adjusted the standard in a few regards based on...
At the moment, - is being redirected to (note the URL scheme); - is being redirected to .
Would a section detailing how to handle branches and merging for the CHANGELOG be helpful?
The CPAN community (Perl) has a (non-mandatory) changelog standard documented in [CPAN::Changes::Spec](https://metacpan.org/dist/CPAN-Changes/view/lib/CPAN/Changes/Spec.pod) since at least 2011.
This PR changes the Swedish title word "Håll" to "För". "Håll" is a litteral translation (approx "Hold a changelog") while "För" is better.
