##// END OF EJS Templates
Mention that we don't do cleanup PRs
Thomas Kluyver -
Show More
@@ -31,6 +31,11 b' Some guidelines on contributing to IPython:'
31 * New features and backwards-incompatible changes should be documented by adding
31 * New features and backwards-incompatible changes should be documented by adding
32 a new file to the [pr](docs/source/whatsnew/pr) directory, see [the README.md
32 a new file to the [pr](docs/source/whatsnew/pr) directory, see [the README.md
33 there](docs/source/whatsnew/pr/README.md) for details.
33 there](docs/source/whatsnew/pr/README.md) for details.
34 * Don't make 'cleanup' pull requests just to change code style.
35 We don't follow any style guide strictly, and we consider formatting changes
36 unnecessary noise.
37 If you're making functional changes, you can clean up the specific pieces of
38 code you're working on.
34
39
35 [Travis](http://travis-ci.org/#!/ipython/ipython) does a pretty good job testing IPython and Pull Requests,
40 [Travis](http://travis-ci.org/#!/ipython/ipython) does a pretty good job testing IPython and Pull Requests,
36 but it may make sense to manually perform tests (possibly with our `test_pr` script),
41 but it may make sense to manually perform tests (possibly with our `test_pr` script),
General Comments 0
You need to be logged in to leave comments. Login now