This document provides guidelines for people who want to contribute to the django-anysign project.
Please use django-anysign bugtracker [1] before starting some work:
- check if the bug or feature request has already been filed. It may have been answered too!
- else create a new ticket.
- if you plan to contribute, tell us, so that we are given an opportunity to give feedback as soon as possible.
- Then, in your commit messages, reference the ticket with some
refs #TICKET-ID
syntax.
- Work in branches.
- Prefix your branch with the ticket ID corresponding to the issue. As an
example, if you are working on ticket #23 which is about contribute
documentation, name your branch like
23-contribute-doc
.
Clone django-anysign repository (adapt to use your own fork):
git clone [email protected]:peopledoc/django-anysign.git
cd django-anysign/
The Makefile is the reference card for usual actions in development environment:
- Install development toolkit with pip [2]:
make develop
. - Run tests with tox [3]:
make test
. - Build documentation:
make documentation
. It builds Sphinx [4] documentation in var/docs/html/index.html. - Release django-anysign project with zest.releaser [5]:
make release
. - Cleanup local repository:
make clean
,make distclean
andmake maintainer-clean
.
See also make help
.
Notes & references
[1] | https://github.com/peopledoc/django-anysign/issues |
[2] | https://pypi.org/project/pip/ |
[3] | https://pypi.org/project/tox/ |
[4] | https://pypi.org/project/Sphinx/ |
[5] | https://pypi.org/project/zest.releaser/ |