22
33Contributions are welcome and very much appreciated!
44
5-
65## Code contributions
76
87We accept code contributions through pull requests.
@@ -12,28 +11,27 @@ In short, this is how that works.
12112 . Create a virtual environment using your tool of choice (e.g. ` virtualenv ` , ` conda ` , etc).
13123 . Install development dependencies:
1413
15- ``` bash
16- $ pip install -r requirements-dev.txt
17- ```
14+ ``` bash
15+ pip install -r requirements-dev.txt
16+ ```
1817
19184 . Make sure all tests pass:
2019
21- ``` bash
22- $ invoke test
23- ```
20+ ``` bash
21+ invoke test
22+ ```
2423
25245 . Start making your changes to the ** master** branch (or branch off of it).
26256 . Make sure all tests still pass:
2726
28- ``` bash
29- $ invoke test
30- ```
27+ ``` bash
28+ invoke test
29+ ```
3130
32317 . Add yourself to the * Contributors* section of ` AUTHORS.md ` .
33328 . Commit your changes and push your branch to GitHub.
34339 . Create a [ pull request] ( https://help.github.com/articles/about-pull-requests/ ) through the GitHub website.
3534
36-
3735During development, use [ pyinvoke] ( http://docs.pyinvoke.org/ ) tasks on the
3836command line to ease recurring operations:
3937
@@ -43,7 +41,6 @@ command line to ease recurring operations:
4341* ` invoke test ` : Run all tests and checks in one swift command.
4442* ` invoke ` : Show available tasks.
4543
46-
4744## Bug reports
4845
4946When [ reporting a bug] ( https://github.com/BlockResearchGroup/compas_assembly/issues ) please include:
@@ -52,7 +49,6 @@ When [reporting a bug](https://github.com/BlockResearchGroup/compas_assembly/iss
5249* Any details about your local setup that might be helpful in troubleshooting.
5350* Detailed steps to reproduce the bug.
5451
55-
5652## Feature requests
5753
5854When [ proposing a new feature] ( https://github.com/BlockResearchGroup/compas_assembly/issues ) please include:
0 commit comments