Hacking:Making pull requests: Difference between revisions

Line 19:

NOTE: INSERT UPDATED, GIT BASED, WORKFLOW EXAMPLE HERE

* As open source community we try to be open as possible. This mean if your changes fix something, extend or add new feature and not goes against our goals we will merge such a patch. Even if this patch is not perfect. This rule guarantee that you will not stuck with requests to fix your changes. We will help you by continue working with your code after merging.

* It is easiest for others to understand your intent if you follow naming conventions. Please use a convention of creating a branch to save your work in the github repository~~. For example, a fix for an issue from the list would go in a branch named issue-xxx~~. See [https://guides.github.com/introduction/git-handbook/ the github handbook] for more information about how to use the github tools.

* It is easiest for others to understand your intent if you follow naming conventions. Please use a convention of creating a branch to save your work in the github repository. See [https://guides.github.com/introduction/git-handbook/ the github handbook] for more information about how to use the github tools.

* Please start your changes from [https://github.com/FashionFreedom/Seamly2D/tree/develop the Seamly2D repository '''develop''' branch]. You may use the fork command to create your own copy of the repository. If you are not sure, please, ask for help in the [https://forum.seamly.net/c/developer forum].