1- .. highlight :: shell
2-
3- ============
4- Contributing
5- ============
1+ # Contributing
62
73Contributions are welcome, and they are greatly appreciated! Every
84little bit helps, and credit will always be given.
95
106You can contribute in many ways:
117
12- Types of Contributions
13- ----------------------
8+ ## Types of Contributions
149
15- Report Bugs
16- ~~~~~~~~~~~
10+ ### Report Bugs
1711
1812Report bugs at https://github.com/Lobosque/python_wpapi/issues .
1913
@@ -23,27 +17,23 @@ If you are reporting a bug, please include:
2317* Any details about your local setup that might be helpful in troubleshooting.
2418* Detailed steps to reproduce the bug.
2519
26- Fix Bugs
27- ~~~~~~~~
20+ ### Fix Bugs
2821
2922Look through the GitHub issues for bugs. Anything tagged with "bug"
3023and "help wanted" is open to whoever wants to implement it.
3124
32- Implement Features
33- ~~~~~~~~~~~~~~~~~~
25+ ### Implement Features
3426
3527Look through the GitHub issues for features. Anything tagged with "enhancement"
3628and "help wanted" is open to whoever wants to implement it.
3729
38- Write Documentation
39- ~~~~~~~~~~~~~~~~~~~
30+ ### Write Documentation
4031
4132Python Wordpress API could always use more documentation, whether as part of the
4233official Python Wordpress API docs, in docstrings, or even on the web in blog posts,
4334articles, and such.
4435
45- Submit Feedback
46- ~~~~~~~~~~~~~~~
36+ ### Submit Feedback
4737
4838The best way to send feedback is to file an issue at https://github.com/Lobosque/python_wpapi/issues .
4939
@@ -54,46 +44,54 @@ If you are proposing a feature:
5444* Remember that this is a volunteer-driven project, and that contributions
5545 are welcome :)
5646
57- Get Started!
58- ------------
47+ ## Get Started!
5948
6049Ready to contribute? Here's how to set up ` python_wpapi ` for local development.
6150
62511 . Fork the ` python_wpapi ` repo on GitHub.
63- 2. Clone your fork locally::
52+ 2 . Clone your fork locally:
6453
54+ ```
6555 $ git clone [email protected] :your_name_here/python_wpapi.git 56+ ```
6657
67583. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development::
6859
60+ ```
6961 $ mkvirtualenv python_wpapi
7062 $ cd python_wpapi/
7163 $ python setup.py develop
64+ ```
7265
73664. Create a branch for local development::
7467
68+ ```
7569 $ git checkout -b name-of-your-bugfix-or-feature
70+ ```
7671
7772 Now you can make your changes locally.
7873
79745. When you're done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox::
8075
76+ ```
8177 $ flake8 python_wpapi tests
8278 $ python setup.py test or py.test
8379 $ tox
80+ ```
8481
8582 To get flake8 and tox, just pip install them into your virtualenv.
8683
87846. Commit your changes and push your branch to GitHub::
8885
86+ ```
8987 $ git add .
9088 $ git commit -m "Your detailed description of your changes."
9189 $ git push origin name-of-your-bugfix-or-feature
90+ ```
9291
93927. Submit a pull request through the GitHub website.
9493
95- Pull Request Guidelines
96- -----------------------
94+ ### Pull Request Guidelines
9795
9896Before you submit a pull request, check that it meets these guidelines:
9997
@@ -105,10 +103,10 @@ Before you submit a pull request, check that it meets these guidelines:
105103 https://travis-ci.org/Lobosque/python_wpapi/pull_requests
106104 and make sure that the tests pass for all supported Python versions.
107105
108- Tips
109- ----
110-
111- To run a subset of tests::
106+ ## Tips
112107
108+ To run a subset of tests:
113109
110+ ```
114111 $ python -m unittest tests.test_python_wpapi
112+ ```
0 commit comments