Skip to content

Commit e795c18

Browse files
committed
Update links in CONTRIBUTING docs
1 parent df119b0 commit e795c18

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

CONTRIBUTING.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Contributing to PHP The Right Way
22

3-
Enjoy [PHP The Right Way](http://phptherightway.com) and want to get
3+
Enjoy [PHP The Right Way](https://phptherightway.com) and want to get
44
involved? Great! There are plenty of ways you can help out.
55

66
Please take a moment to review this document in order to make the contribution
@@ -20,7 +20,7 @@ content and generally [submitting pull requests](#pull-requests), but please
2020
respect the following restrictions:
2121

2222
* Please **do not** use the issue tracker for personal support requests (use
23-
[Stack Overflow](http://stackoverflow.com/questions/tagged/php) or IRC).
23+
[Stack Overflow](https://stackoverflow.com/questions/tagged/php) or IRC).
2424

2525
* Please **do not** derail or troll issues. Keep the discussion on topic and
2626
respect the opinions of others.
@@ -36,8 +36,8 @@ change is accepted if seen as constructive.
3636
Adhering to the following process is the best way to get your work
3737
included in the project:
3838

39-
1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
40-
and configure the remotes:
39+
1. [Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) the
40+
project, clone your fork, and configure the remotes:
4141

4242
```bash
4343
# Clone your fork of the repo into the current directory
@@ -72,9 +72,9 @@ included in the project:
7272
```
7373

7474
5. Commit your changes in logical chunks. Please adhere to these [git commit
75-
message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
75+
message guidelines](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
7676
or your content is unlikely be merged into the main project. Use Git's
77-
[interactive rebase](https://help.github.com/articles/about-git-rebase/)
77+
[interactive rebase](https://docs.github.com/en/get-started/using-git/about-git-rebase)
7878
feature to tidy up your commits before making them public.
7979
8080
6. Locally merge (or rebase) the upstream development branch into your topic branch:
@@ -89,20 +89,20 @@ included in the project:
8989
git push origin <topic-branch-name>
9090
```
9191
92-
8. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
92+
8. [Open a Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
9393
with a clear title and description.
9494
9595
9696
## Contribution Agreement and Usage
9797
9898
By submitting a pull request to this repository, you agree to allow the project
9999
owners to license your work under the the terms of the [Creative Commons Attribution-NonCommercial-ShareAlike
100-
3.0 Unported License](http://creativecommons.org/licenses/by-nc-sa/3.0/).
100+
3.0 Unported License](https://creativecommons.org/licenses/by-nc-sa/3.0/).
101101
102102
The same content and license will be used for all PHP The Right Way publications,
103103
including - but not limited to:
104104
105-
* [phptherightway.com](http://phptherightway.com)
105+
* [phptherightway.com](https://phptherightway.com)
106106
* Translations of phptherightway.com
107107
* [LeanPub: PHP The Right Way](https://leanpub.com/phptherightway/)
108108
* Translations of "LeanPub: PHP The Right Way"

0 commit comments

Comments
 (0)