Skip to content

Commit b2cc576

Browse files
authored
chore(doc): Updated the come broken contributing guideline links (#174)
1 parent 31a49b5 commit b2cc576

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

CONTRIBUTING.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ First of all, **thank you** for contributing, **you are awesome**!
44

55
Everybody should be able to help. Here's how you can do it:
66

7-
1. [Fork it](https://github.com/jolicode/slack-php-api/fork_select)
7+
1. [Fork it](https://github.com/jolicode/slack-php-api/fork)
88
2. improve it
99
3. submit a [pull request](https://help.github.com/articles/creating-a-pull-request)
1010

@@ -20,20 +20,20 @@ Here's some tips to make you the best contributor ever:
2020
Here are a few rules to follow in order to ease code reviews, and discussions
2121
before maintainers accept and merge your work.
2222

23-
* You MUST follow the [PSR-1](http://www.php-fig.org/psr/1/) and
24-
[PSR-2](http://www.php-fig.org/psr/2/) (see [Rules](#rules)).
23+
* You MUST follow the [PSR-1](https://www.php-fig.org/psr/psr-1/) and
24+
[PSR-12](https://www.php-fig.org/psr/psr-12/) (see [Rules](#rules)).
2525
* You MUST run the test suite (see [Green tests](#green-tests)).
2626
* You MUST write (or update) unit tests.
2727
* You SHOULD write documentation.
2828

2929
Please, write [commit messages that make
30-
sense](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html),
31-
and [rebase your branch](http://git-scm.com/book/en/Git-Branching-Rebasing)
30+
sense](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html),
31+
and [rebase your branch](https://git-scm.com/book/en/Git-Branching-Rebasing)
3232
before submitting your Pull Request (see also how to [keep your
3333
fork up-to-date](#keeping-your-fork-up-to-date)).
3434

3535
One may ask you to [squash your
36-
commits](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)
36+
commits](https://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)
3737
too. This is used to "clean" your Pull Request before merging it (we don't want
3838
commits such as `fix tests`, `fix 2`, `fix 3`, etc.).
3939

@@ -53,7 +53,7 @@ make test
5353

5454
## Standard code
5555

56-
Use [PHP CS fixer](http://cs.sensiolabs.org/) to make your code compliant with
56+
Use [PHP CS fixer](https://cs.symfony.com/) to make your code compliant with
5757
our coding standards:
5858

5959
```shell
@@ -65,7 +65,6 @@ make cs
6565
To keep your fork up-to-date, you should track the upstream (original) one
6666
using the following command:
6767

68-
6968
```shell
7069
git remote add upstream https://github.com/jolicode/slack-php-api.git
7170
```
@@ -88,5 +87,4 @@ git push -f origin <your-branch>
8887

8988
Your pull request will be automatically updated.
9089

91-
9290
Thank you!

0 commit comments

Comments
 (0)