Skip to content

Latest commit

 

History

History
84 lines (53 loc) · 2.12 KB

CONTRIBUTING.rst

File metadata and controls

84 lines (53 loc) · 2.12 KB

Contributing

This document provides guidelines for people who want to contribute to the django-adobesign project.

Create tickets

Please use django-adobesign bugtracker 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.

Use topic branches

  • 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.
  • If you work in a development branch and want to refresh it with changes from master, please rebase [1] or merge-based rebase [2], i.e. do not merge master.

Fork, clone

Clone django-adobesign repository (adapt to use your own fork):

git clone git@github.com:novapost/django-adobesign.git
cd django-adobesign/

Usual actions

The Makefile is the reference card for usual actions in development environment:

  • Install development toolkit with pip [3]: make develop.
  • Run tests with tox [4]: make test.
  • Build documentation: make documentation. It builds Sphinx [5] documentation in var/docs/html/index.html.
  • Release django-adobesign project with zest.releaser [6]: make release.
  • Cleanup local repository: make clean, make distclean and make maintainer-clean.

See also make help.

Notes & references

[1]http://git-scm.com/book/en/Git-Branching-Rebasing
[2]https://tech.people-doc.com/psycho-rebasing.html
[3]https://pypi.org/project/pip/
[4]https://pypi.org/project/tox/
[5]https://pypi.org/project/Sphinx/
[6]https://pypi.org/project/zest.releaser/