aboutsummaryrefslogtreecommitdiff
path: root/.github
diff options
context:
space:
mode:
authorVasilii Artemchuk <[email protected]>2017-09-24 14:22:42 +0300
committerPatrick H. Lauke <[email protected]>2017-09-24 13:22:42 +0200
commit3abf8a0e5525d30914ce37ebb98240a476cb6f17 (patch)
tree5f9817e8f03a01ed210cb5356946823786e2c694 /.github
parentfd56ea370c371345cd9a34e65a615853ad882577 (diff)
downloadbootstrap-3abf8a0e5525d30914ce37ebb98240a476cb6f17.tar.xz
bootstrap-3abf8a0e5525d30914ce37ebb98240a476cb6f17.zip
Updated github help links (#24071)
Diffstat (limited to '.github')
-rw-r--r--.github/CONTRIBUTING.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index 6fc088d6b..523282f2a 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -151,7 +151,7 @@ documentation source files and is managed separately by the Bootstrap Core Team.
Adhering to the following process is the best way to get your work
included in the project:
-1. [Fork](https://help.github.com/fork-a-repo/) the project, clone your fork,
+1. [Fork](https://help.github.com/articles/fork-a-repo/) the project, clone your fork,
and configure the remotes:
```bash
@@ -180,7 +180,7 @@ included in the project:
4. Commit your changes in logical chunks. Please adhere to these [git commit
message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
or your code is unlikely be merged into the main project. Use Git's
- [interactive rebase](https://help.github.com/articles/interactive-rebase)
+ [interactive rebase](https://help.github.com/articles/about-git-rebase/)
feature to tidy up your commits before making them public.
5. Locally merge (or rebase) the upstream development branch into your topic branch:
@@ -195,7 +195,7 @@ included in the project:
git push origin <topic-branch-name>
```
-7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
+7. [Open a Pull Request](https://help.github.com/articles/about-pull-requests/)
with a clear title and description against the `master` branch.
**IMPORTANT**: By submitting a patch, you agree to allow the project owners to