@@ -15,7 +15,7 @@ Types of Contributions
1515Report Bugs
1616~~~~~~~~~~~
1717
18- Report bugs at https://github.com/mhalagan- nmdp/pyars /issues.
18+ Report bugs at https://github.com/nmdp-bioinformatics/py-ard /issues.
1919
2020If you are reporting a bug, please include:
2121
@@ -38,14 +38,14 @@ and "help wanted" is open to whoever wants to implement it.
3838Write Documentation
3939~~~~~~~~~~~~~~~~~~~
4040
41- pyARS could always use more documentation, whether as part of the
42- official pyARS docs, in docstrings, or even on the web in blog posts,
41+ py-ard could always use more documentation, whether as part of the
42+ official py-ard docs, in docstrings, or even on the web in blog posts,
4343articles, and such.
4444
4545Submit Feedback
4646~~~~~~~~~~~~~~~
4747
48- The best way to send feedback is to file an issue at https://github.com/mhalagan- nmdp/pyars /issues.
48+ The best way to send feedback is to file an issue at https://github.com/nmdp-bioinformatics/py-ard /issues
4949
5050If you are proposing a feature:
5151
@@ -57,32 +57,40 @@ If you are proposing a feature:
5757Get Started!
5858------------
5959
60- Ready to contribute? Here's how to set up `pyars ` for local development.
60+ Ready to contribute? Here's how to set up `py-ard ` for local development.
6161
62- 1. Fork the `pyars ` repo on GitHub.
62+ 1. Fork the `py-ard ` repo on GitHub.
63632. Clone your fork locally::
6464
65- $ git clone [email protected] :your_name_here/pyars .git 65+ $ git clone [email protected] :your_name_here/py-ard .git 6666
67- 3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development::
67+ 3. Install your local copy into a venv. This is how you set up your fork for local development::
6868
69- $ mkvirtualenv pyars
70- $ cd pyars/
71- $ python setup.py develop
69+ $ cd py-ard
70+ $ make venv
71+ $ source venv/bin/activate
72+ $ make install
7273
73744. Create a branch for local development::
7475
7576 $ git checkout -b name-of-your-bugfix-or-feature
7677
7778 Now you can make your changes locally.
7879
79- 5. When you're done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox ::
80+ 5. When you're done making changes, make sure you have a corresponding test, check that all your changes pass flake8 and the tests::
8081
81- $ flake8 pyars tests
82- $ python setup.py test or py.test
83- $ tox
82+ $ make test
83+ $ make lint
8484
85- To get flake8 and tox, just pip install them into your virtualenv.
85+ To get test runners, you would to have done `make install` earlier.
86+
87+ To run behavior-driven development (BDD) tests locally via the behave framework, run::
88+
89+ $ behave
90+
91+ Run unit-tests::
92+
93+ $ python -m unittest tests.test_pyard
8694
87956. Commit your changes and push your branch to GitHub::
8896
@@ -101,14 +109,5 @@ Before you submit a pull request, check that it meets these guidelines:
1011092. If the pull request adds functionality, the docs should be updated. Put
102110 your new functionality into a function with a docstring, and add the
103111 feature to the list in README.rst.
104- 3. The pull request should work for Python 2.6, 2.7, 3.3, 3.4 and 3.5, and for PyPy. Check
105- https://travis-ci.org/mhalagan-nmdp/pyars/pull_requests
112+ 3. The pull request should work for Python 3.8 and higher.
106113 and make sure that the tests pass for all supported Python versions.
107-
108- Tips
109- ----
110-
111- To run a subset of tests::
112-
113-
114- $ python -m unittest tests.test_pyars
0 commit comments