Contributions are welcome, and they are greatly appreciated!
When reporting a bug, always include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
This could always use more documentation, whether in the form of docstrings, additions to the man page or the creation of a manual (currently non-existent).
The best way to send feedback is to file an issue at https://github.com/openSUSE/dbxincluder/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
To set up dbxincluder for local development:
-
Clone your fork locally:
git clone git@github.com:your_name_here/dbxincluder.git
-
Create a branch for local development:
git flow feature start name-of-your-bugfix-or-feature
Now you can make your changes locally.
-
When you're done making changes, run all the checks, doc builder and spell checker with tox:
tox
-
Commit your changes and push your branch to GitHub:
git add . git commit -m "Your detailed description of your changes." git flow feature publish
-
Submit a pull request through the GitHub website.
If you need some code review or feedback while you're developing the code just make the pull request.
For merging, you should:
- Include passing tests (run
tox
) [1]. - Update documentation when there's new API, functionality etc.
- Add a note to
CHANGELOG.rst
about the changes. - Add yourself to
AUTHORS.rst
.
To run a subset of tests:
tox -e envname -- py.test -k test_myfeature
To run all the test environments in parallel (you need to pip install detox
):
detox
[1] If you don't have all the necessary Python versions available locally, you can rely on Travis - it will run the tests for each change you add to the pull request. However, that is a bit slower.