aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeremyRand <biolizard89@gmail.com>2019-03-11 16:03:49 +0000
committerJeremyRand <biolizard89@gmail.com>2019-03-11 16:03:49 +0000
commit228e80608d93a6359b9846fd3d05a199fd488ddd (patch)
treeec7da9ee25723803fe7e4da56ed91cfe8b041e4d
parentc94852e7912eb0881eb38af28cd2e3076e53e393 (diff)
Enable TLS in link to chris.beams.io
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 139fe7dc52..82c96efa0c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -62,7 +62,7 @@ Commit messages should be verbose by default consisting of a short subject line
paragraph(s), unless the title alone is self-explanatory (like "Corrected typo
in init.cpp") in which case a single title line is sufficient. Commit messages should be
helpful to people reading your code in the future, so explain the reasoning for
-your decisions. Further explanation [here](http://chris.beams.io/posts/git-commit/).
+your decisions. Further explanation [here](https://chris.beams.io/posts/git-commit/).
If a particular commit references another issue, please add the reference. For
example: `refs #1234` or `fixes #4321`. Using the `fixes` or `closes` keywords