From f744c2553eb71f5916a913d32ea07bb67b3a3187 Mon Sep 17 00:00:00 2001 From: Scott Albertson Date: Wed, 1 Aug 2018 14:59:06 -0700 Subject: [PATCH] Use https when linking to chris.beams.io Why not link to How to [Write a Git Commit Message](https://chris.beams.io/posts/git-commit/) using HTTPS, it's going to redirect anyway. --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 1dda90817..8a10d5e80 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -164,7 +164,7 @@ history and triaging bugs much easier. Git commit messages have a very terse summary in the first line of the commit message, followed by an empty line, followed by a more verbose description or a List of changed things. For examples, please refer to the excellent [How to -Write a Git Commit Message](http://chris.beams.io/posts/git-commit/). +Write a Git Commit Message](https://chris.beams.io/posts/git-commit/). If you change/add multiple different things that aren't related at all, try to make several smaller commits. This is much easier to review. Using `git add -p`