From 11b6aae39010ebdb3141f3bed505fde368040957 Mon Sep 17 00:00:00 2001 From: Richard Littauer Date: Tue, 17 Jan 2017 15:12:59 -0300 Subject: [PATCH] Merge js-project and js-commit guidelines See https://github.com/ipfs/community/issues/225 --- js-commit-guidelines.md | 99 --------------------------- js-project-guidelines.md | 143 ++++++++++++++++++++++++++++++++++----- 2 files changed, 127 insertions(+), 115 deletions(-) delete mode 100644 js-commit-guidelines.md diff --git a/js-commit-guidelines.md b/js-commit-guidelines.md deleted file mode 100644 index 984a0a3d..00000000 --- a/js-commit-guidelines.md +++ /dev/null @@ -1,99 +0,0 @@ -# Git Commit Guidelines - -We have very precise rules over how our git commit messages can be formatted. -This leads to more readable messages that are easy to follow when -looking through the project history. But also, -we use the git commit messages to generate the change log. - -The commit message formatting can be added using a typical git workflow or -through the use of a CLI wizard ([Commitizen](https://github.com/commitizen/cz-cli)). - -### Commit Message Format -Each commit message consists of a header, a body and a footer. -The header has a special format that includes a type, a scope and a subject: - -``` -(): - - - -