summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkkkkkkkk <seankao31@gmail.com>2016-11-19 17:57:34 +0800
committerkkkkkkkk <seankao31@gmail.com>2016-11-19 17:57:34 +0800
commit625a86403d224918c607ae69593f2a7caaaf5bfb (patch)
treecbe0b93d30058da8e1b53dae2ea19a427df5f496
parent78e34d8add4bc1d5e4d820a3a8e8636d5226c427 (diff)
downloadgitlab-ce-625a86403d224918c607ae69593f2a7caaaf5bfb.tar.gz
fix typo in gitlab_flow.md ('munch'->'much')
-rw-r--r--doc/workflow/gitlab_flow.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/workflow/gitlab_flow.md b/doc/workflow/gitlab_flow.md
index 2215f37b81a..c228ea72f22 100644
--- a/doc/workflow/gitlab_flow.md
+++ b/doc/workflow/gitlab_flow.md
@@ -279,7 +279,7 @@ The trick is to use the merge/pull request with multiple commits when your work
The commit message should reflect your intention, not the contents of the commit.
The contents of the commit can be easily seen anyway, the question is why you did it.
An example of a good commit message is: "Combine templates to dry up the user views.".
-Some words that are bad commit messages because they don't contain munch information are: change, improve and refactor.
+Some words that are bad commit messages because they don't contain much information are: change, improve and refactor.
The word fix or fixes is also a red flag, unless it comes after the commit sentence and references an issue number.
To see more information about the formatting of commit messages please see this great [blog post by Tim Pope](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).