|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (14)
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|https://github.com/teltek/Galicaster]. Please follow the recommendations below and, if possible, nice-to-have tips.
*RECOMMENDATIONS:*
{tip}Thank you so much for your Contributions \!\!{tip}
h5. *RECOMMENDATIONS:*
h5. *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 forked branch in synch. Features or bug fixes that don't merge cleanly will be rejected.{color}
# {color:#222222}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){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}
# {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}
{column}
{column:width=50%}
{column:width=50%}
{center}
*We are using Git this way:*
!Galicaster.gitflow-model v02b.jpg|border=1,width=3500!
Inspired on Vicent Driessen [Git branching model|http://nvie.com/posts/a-successful-git-branching-model/]
Inspired {center}
on...
{column}{section}