Loading sub-menu...

Galicaster Code Contributions

Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

This page describes how to contribute to Galicaster Code. All Galicaster development and bugfixing is done on Galicaster public Git repository. Please follow the recommendations below and, if possible, nice-to-have tips. 

Thank you so much for your Contributions !!
  1. All contributions must be forked from the "master" branch.
  2. Frequently pull changes made at the master branch, to keep your feature branch/fork in synch. Features or bug fixes that don't merge cleanly will be rejected.
  3. Send us a pull request when your feature or bug fix is ready. Please do not group several bug fixes or features in the same request (where possible)
  4. Use descriptive commit messages and include a reference to the relevant issue, if any (e.g. "Fixed so-and-so bug, issue #15").
  1. Add unit tests to the features developed.
  2. Check your code quality before sending the pull request. You may use tools such as pep8 or pychecker.
Important Notice about Licensing

Patches that fix a bug or provide a minor enhancement might be accepted without a Contributor License Agreement being completed. Major enhancements require a valid Contributor License Agreement

We are using Git this way:

Inspired on Vicent Driessen Git branching model

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.