If you build software, keep a changelog.
Go to file
Olivier Lacan 01a420df24 Add new project logo
Also downcased all uses of the word "changelog"
2017-04-24 17:05:25 -04:00
source Use the correct value for lang and hreflang 2017-03-25 10:23:32 -04:00
.editorconfig Add charset config to .editorconfig 2016-07-29 01:59:22 +09:00
.gitignore @jswanner says I should ignore this 2016-08-05 20:00:22 -04:00
.ruby-version Upgrade to Middleman 4.1.10 2016-08-06 01:37:12 -04:00
CHANGELOG.md Add latest fixes to change log 2017-01-18 03:43:45 +01:00
CONTRIBUTING.md Rewrite README to focus on development 2016-08-06 02:02:30 -04:00
Gemfile Upgrade to Middleman 4.1.10 2016-08-06 01:37:12 -04:00
Gemfile.lock Upgrade to Middleman 4.1.10 2016-08-06 01:37:12 -04:00
LICENSE Convert static files to a Middleman app. 2015-10-18 16:35:53 -04:00
README.md Add new project logo 2017-04-24 17:05:25 -04:00
Rakefile Convert static files to a Middleman app. 2015-10-18 16:35:53 -04:00
config.rb Add Czech language translation 2017-03-01 15:34:23 +01:00
routes.rb Start versioning from 0.3.0 2016-05-16 15:20:26 +02:00

README.md

Keep a Changelog

version license

Dont let your friends dump git logs into changelogs™

This repository generates http://keepachangelog.com/.

Development

Dependencies

Installation

  • git clone https://github.com/olivierlacan/keep-a-changelog.git
  • cd keep-a-changelog
  • bundle install
  • middleman starts the local development server at http://localhost:4567

Deployment

  • rake publish builds and pushes to the gh-pages branch

Translations

Create a new directory in source/ named after the ISO 639-1 code for the language you wish to translate Keep a Changelog to. For example, assuming you want to translate to French Canadian:

  • create the source/fr-CA directory.
  • duplicate the source/en-US/index.html.haml file in source/fr-CA.
  • edit source/fr-CA/index.html.haml until your translation is ready.
  • commit your changes to your own fork
  • submit a Pull Request with your changes

It may take some time to review your submitted Pull Request. Try to involve a few native speakers of the language you're translating to in the Pull Request comments. They'll help review your translation for simple mistakes and give us a better idea of whether your translation is accurate.

Thank you for your help improving software one changelog at a time!