Fork from master and send pull requests to master

Master is essentially our dev branch.

[CI skip]
This commit is contained in:
Hugo 2014-11-06 13:01:42 +02:00
parent 6d7c010bed
commit b5315eb59b

View File

@ -2,13 +2,13 @@
## Fixes, Features and Changes ## Fixes, Features and Changes
Send a pull request. We'll generally want documentation and [tests](Tests/README.rst) for new features. Tests or documentation on their own are also welcomed. Feel free to ask questions as an [issue](https://github.com/python-pillow/Pillow/issues/new) or on IRC (irc.freenode.net, #pil) Send a pull request to the master branch. We'll generally want documentation and [tests](Tests/README.rst) for new features. Tests or documentation on their own are also welcomed. Feel free to ask questions as an [issue](https://github.com/python-pillow/Pillow/issues/new) or on IRC (irc.freenode.net, #pil)
- Fork the repo - Fork the repo
- Make a branch - Make a branch from master
- Add your changes + Tests - Add your changes + Tests
- Run the test suite. Try to run on both Python 2.x and 3.x, or you'll get tripped up. You can enable [Travis CI on your repo](https://travis-ci.org/profile/) to catch test failures prior to the pull request, and [Coveralls](https://coveralls.io/repos/new) to see if the changed code is covered by tests. - Run the test suite. Try to run on both Python 2.x and 3.x, or you'll get tripped up. You can enable [Travis CI on your repo](https://travis-ci.org/profile/) to catch test failures prior to the pull request, and [Coveralls](https://coveralls.io/repos/new) to see if the changed code is covered by tests.
- Push to your fork, and make a pull request. - Push to your fork, and make a pull request onto master.
A few guidelines: A few guidelines:
- Try to keep any code commits clean and separate from reformatting commits. - Try to keep any code commits clean and separate from reformatting commits.