kennethreitz/pipenv
1
0
Fork 0
mirror of https://github.com/kennethreitz/pipenv.git synced 2026-06-05 22:50:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Use generic enumerated list markers

Browse Source
This commit is contained in:
Brianna Laugher
2018-10-30 11:02:31 +11:00
committed by GitHub
parent 0539e07dca
commit 511c0e5adb
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/dev/contributing.rst
+8 -8
View File
@@ -85,18 +85,18 @@ Steps for Submitting Code
When contributing code, you'll want to follow this checklist:
0. Understand our `development philosophy`_.
1. Fork the repository on GitHub.
2. Set up your :ref:`dev-setup`
3. Run the tests (:ref:`testing`) to confirm they all pass on your system.
#. Understand our `development philosophy`_.
#. Fork the repository on GitHub.
#. Set up your :ref:`dev-setup`
#. Run the tests (:ref:`testing`) to confirm they all pass on your system.
If they don't, you'll need to investigate why they fail. If you're unable
to diagnose this yourself, raise it as a bug report by following the guidelines
in this document: :ref:`bug-reports`.
4. Write tests that demonstrate your bug or feature. Ensure that they fail.
5. Make your change.
6. Run the entire test suite again, confirming that all tests pass *including
#. Write tests that demonstrate your bug or feature. Ensure that they fail.
#. Make your change.
#. Run the entire test suite again, confirming that all tests pass *including
the ones you just added*.
6. Send a GitHub Pull Request to the main repository's ``master`` branch.
#. Send a GitHub Pull Request to the main repository's ``master`` branch.
GitHub Pull Requests are the expected method of code collaboration on this
project.