Skip to content
This repository has been archived by the owner on Jan 24, 2022. It is now read-only.

Commit

Permalink
Merge pull request #498 from nicolasleger/patch-1
Browse files Browse the repository at this point in the history
Contributing : Use HTTPS links
  • Loading branch information
Jonathan Claudius authored Apr 15, 2019
2 parents 1947d80 + 46da2c8 commit 9f893cc
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,17 +27,17 @@ inclusion, but sending a pull request is much more awesome.

If you want your pull requests to be accepted, please follow the following guidelines:

- [**Add tests!**](http://rspec.info/) Your patch won't be accepted (or will be delayed) if it doesn't have tests.
- [**Add tests!**](https://rspec.info/) Your patch won't be accepted (or will be delayed) if it doesn't have tests.

- [**Document any change in behaviour**](http://yardoc.org/) Make sure the README and any other
- [**Document any change in behaviour**](https://yardoc.org/) Make sure the README and any other
relevant documentation are kept up-to-date.

- [**Create topic branches**](https://github.com/dchelimsky/rspec/wiki/Topic-Branches) Don't ask us to pull from your master branch.

- [**One pull request per feature**](https://help.github.com/articles/using-pull-requests) If you want to do more than one thing, send
multiple pull requests.

- [**Send coherent history**](http://stackoverflow.com/questions/6934752/git-combining-multiple-commits-before-pushing) Make sure each individual commit in your pull
- [**Send coherent history**](https://stackoverflow.com/questions/6934752/git-combining-multiple-commits-before-pushing) Make sure each individual commit in your pull
request is meaningful. If you had to make multiple intermediate commits while
developing, please squash them before sending them to us.

Expand Down

0 comments on commit 9f893cc

Please sign in to comment.