From 4aaff15b6827113789d1bb23136512ad05789cee Mon Sep 17 00:00:00 2001 From: Stefan Peters Date: Thu, 9 Aug 2018 13:26:42 +0200 Subject: [PATCH] Fix mistake in Closing Issues via Commit Messages The issue will be closed as soon as the commit is committed to the **repository's default branch**, not the master branch. I noticed this because we're using a different default branch for one of our projects. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c1dcfaf..4afcde8 100644 --- a/README.md +++ b/README.md @@ -256,7 +256,7 @@ https://github.com/rails/rails/blob/master/activemodel/lib/active_model.rb#L53-L ![Line Highlighting](http://i.imgur.com/8AhjrCz.png) ### Closing Issues via Commit Messages -If a particular commit fixes an issue, any of the keywords `fix/fixes/fixed`, `close/closes/closed` or `resolve/resolves/resolved`, followed by the issue number, will close the issue once it is committed to the master branch. +If a particular commit fixes an issue, any of the keywords `fix/fixes/fixed`, `close/closes/closed` or `resolve/resolves/resolved`, followed by the issue number, will close the issue once it is committed to the repository's default branch. ```bash $ git commit -m "Fix screwup, fixes #12"