@@ -5,16 +5,16 @@ Bugs and Features
5
5
-----------------
6
6
7
7
If you have found any bugs or would like to request a new feature, please do
8
- check if there is an existing issue already filed for the same, in the
9
- project's GitHub ` issue tracker `_ . If not, please file a new issue.
8
+ check in the project's GitHub ` issue tracker `_, if there is a similar existing
9
+ issue already filed . If not, please file a new issue.
10
10
11
11
If you want to help out by fixing bugs, choose an issue from the `issue
12
12
tracker `_ to work on and claim it by posting a comment saying "I would like to
13
13
work on this.". Feel free to ask any doubts in the issue thread.
14
14
15
15
Once you have implemented the feature to an extent, go ahead and file a pull
16
- request, following the tips below. File a pull request early to get feedback as
17
- early as possible.
16
+ request by following the tips below. File a pull request early to get feedback
17
+ as early as possible.
18
18
19
19
Pull Requests
20
20
-------------
@@ -27,8 +27,8 @@ land a single large feature.
27
27
Checklist:
28
28
29
29
1. All pull requests *must * be made against the ``master `` branch.
30
- 2. Include tests for any functionality you implement. Any contributions helping
31
- improve existing tests is welcome.
30
+ 2. Include tests for any functionality you implement. Contributions that
31
+ improve existing tests are welcome.
32
32
3. Update documentation as necessary and provide documentation for any new
33
33
functionality.
34
34
4. In case of UI changes, please include screenshots.
0 commit comments