|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (9)
View Page History
...
{section} {column:width=50%}
*INTRODUCTION*
h5. *INTRODUCTION*
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 \!\!
{tip}Thank you so much for your Contributions \!\!{tip}
h5. *RECOMMENDATIONS:*
*RECOMMENDATIONS:*
# {color:#222222}All contributions must be forked from the "master" branch.{color}
# {color:#222222}Frequently pull changes made at the master branch, to keep your feature branch in synch. Features or bug fixes that don't merge cleanly will be rejected.{color}
# {color:#222222}Frequently pull changes made at the master branch, to keep your feature branch in synch. Features or bug fixes that don't merge cleanly will be rejected.{color}
...# {color:#222222}Use descriptive commit messages and include a reference to the relevant issue, if any (e.g. "Fixed so-and-so bug, issue #15").{color}
h5. {color:#222222}{*}NICE TO HAVE:*{color}
# {color:#222222}Add unit tests to the features developed.{color}
# {color:#222222}Check your code quality before sending the pull request. You may use tools such as pep8 or pychecker.{color}
# {color:#222222}Check your code quality before sending the pull request. You may use tools such as pep8 or pychecker.{color}
h5. {color:#222222}Important Notice about Licensing{color}
{color:#353735}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. {color}
{column}
...