@@ -18,7 +18,7 @@ New to here
18
18
Any issue with good first issue tag on it is a great place to start! Feel free to ask any questions here.
19
19
20
20
Don't know how to start
21
- ~~~~~~~~~~~
21
+ ~~~~~~~~~~~~~~~~~~~~~~~
22
22
23
23
Review codebases and PRs can give you quite a knowledge to know what's going on here!
24
24
@@ -39,8 +39,8 @@ Fix Bugs
39
39
Look through the GitHub issues for bugs. Anything tagged with "bug"
40
40
is open to whoever wants to implement it.
41
41
42
- Implement Features & imporvments
43
- ~~~~~~~~~~~~~~~~~~
42
+ Implement Features & improvments
43
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
44
44
45
45
Look through the GitHub issues for features. Anything tagged with "feature" or "improvments"
46
46
is open to whoever wants to implement it.
@@ -70,7 +70,7 @@ Get Started!
70
70
Ready to contribute? Here's how to set up `scrapy-redis ` for local development.
71
71
72
72
Setup environment
73
- ~~~~~~~~~~~~~~~
73
+ ~~~~~~~~~~~~~~~~~
74
74
75
75
1. Fork the `scrapy-redis ` repo on GitHub.
76
76
2. Clone your fork locally::
@@ -93,7 +93,7 @@ Setup environment
93
93
Now you can make your changes locally.
94
94
95
95
Setup testing environment
96
- ~~~~~~~~~~~~~~~
96
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
97
97
98
98
1. When you're done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox::
99
99
@@ -128,9 +128,7 @@ Before you submit a pull request, check that it meets these guidelines:
128
128
2. If the pull request adds functionality, the docs should be updated. Put
129
129
your new functionality into a function with a docstring, and add the
130
130
feature to the list in README.rst.
131
- 3. The pull request should work for Python 2.6, 2.7, 3.3, 3.4 and 3.5, and for PyPy. Check
132
- https://travis-ci.org/rolando/scrapy-redis/pull_requests
133
- and make sure that the tests pass for all supported Python versions.
131
+ 3. Make sure that the tests pass for all supported Python versions.
134
132
135
133
Tips
136
134
----
0 commit comments