aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCarl Suster <carl@contraflo.ws>2015-09-23 19:10:01 +0200
committerCarl Suster <carl@contraflo.ws>2015-09-23 19:10:01 +0200
commit5778fded8b14e289ffb59f1fdb80960434455475 (patch)
tree263fb798a6031b7b70abb1c568021157b97430de
parent23aad6abc4ed1aafb425f6e09334c4e35ad146ac (diff)
parent75fc01c84115f17b162d8585caf8d157bac21dbb (diff)
downloadgitignore-5778fded8b14e289ffb59f1fdb80960434455475.tar.gz
gitignore-5778fded8b14e289ffb59f1fdb80960434455475.zip
Merge pull request #1668 from github/jdennes/https-help-urls
Use https for all Help URLs
-rw-r--r--README.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/README.md b/README.md
index 14042e94..5c4d20df 100644
--- a/README.md
+++ b/README.md
@@ -31,17 +31,17 @@ high quality, we request that contributions adhere to the following guidelines.
- **Provide a link to the application or project’s homepage**. Unless it’s
extremely popular, there’s a chance the maintainers don’t know about or use
the language, framework, editor, app, or project your change applies to.
-
+
- **Provide links to documentation** supporting the change you’re making.
Current, canonical documentation mentioning the files being ignored is best.
If documentation isn’t available to support your change, do the best you can
to explain what the files being ignored are for.
-
+
- **Explain why you’re making a change**. Even if it seems self-evident, please
take a sentence or two to tell us why your change or addition should happen.
It’s especially helpful to articulate why this change applies to *everyone*
who works with the applicable technology, rather than just you or your team.
-
+
- **Please consider the scope of your change**. If your change specific to a
certain language or framework, then make sure the change is made to the
template for that language or framework, rather than to the template for an
@@ -70,9 +70,9 @@ Here’s how we suggest you go about proposing a change to this project:
Using the web-based interface to make changes is fine too, and will help you
by automatically forking the project and prompting to send a pull request too.
-[fork]: http://help.github.com/forking/
+[fork]: https://help.github.com/articles/fork-a-repo/
[branch]: https://help.github.com/articles/creating-and-deleting-branches-within-your-repository
-[pr]: http://help.github.com/pull-requests/
+[pr]: https://help.github.com/articles/using-pull-requests/
## License