https://www.wiki.synfig.org/index.php?action=history&feed=atom&title=Dev%3AGit_Fundamentals 2026-05-31T15:56:07Z Revision history for this page on the wiki MediaWiki 1.26.3 https://www.wiki.synfig.org/index.php?title=Dev:Git_Fundamentals&diff=21455&oldid=prev 2016-02-17T23:31:15Z

<p>Synfig git fundamentals forum Postby kinderp + djay comments</p> <p><b>New page</b></p><div>Would like to fix your ideas about branches on synfig and its git workflow ?<br /> <br /> Let's start :)<br /> <br /> =Branches=<br /> <br /> The branches are:<br /> [me@host synfig]$ git branch -r<br /> origin/0.64.2<br /> origin/0.64.x<br /> origin/1.0.x<br /> origin/HEAD -&gt; origin/master<br /> origin/dev-1.0.1<br /> origin/eldruin_new_cairo_core<br /> origin/eldruin_transformation_matrix<br /> origin/genete_cairo_core<br /> origin/genete_new_cairo_core<br /> origin/master<br /> <br /> * {{literal|master}} is the stable branch<br /> * {{literal|eldruin_new_cairo_core}}, {{literal|eldruin_transformation_matrix}}, {{literal|genete_cairo_core}}, {{literal|genete_new_cairo_core}}, are username_feature branches where new features are coded and then merged to master<br /> * {{literal|0.64.2}} are the branches of the old releases.<br /> * {{literal|0.64.x}}, {{literal|1.0.x}} are the bug fix branch. Example, the 1.0.x version. Last stable from this branch is 1.0.2. This is where a 1.0.3 could be baked.<br /> <br /> Stable branchs are tagged:<br /> [me@host synfig]$ git tag<br /> 0.64.1<br /> 0.64.1-rc1<br /> 0.64.1-rc2<br /> 0.64.2<br /> 0.64.3<br /> 1.0<br /> 1.0.1<br /> 1.0.2<br /> ...<br /> <br /> =Workflow=<br /> To contribute i should:<br /> * fork synfig on github<br /> * clone my forked repo, {{literal|origin}} for convention, in my local machine<br /> * add original synfig repo, {{literal|upstream}} for convention, with <br /> [me@host synfig]$ git remote add upstream ...<br /> <br /> At this point i haven in my local machine, all xx upstream branches, all xx origin branches and one master local branch.<br /> <br /> It's recommanded to create a branch from updated master for hosting your contribution<br /> $ git checkout master<br /> $ git fetch upstream<br /> $ git rebase upstream/master<br /> $ git branch me_mybranch<br /> $ git checkout me_mybranch<br /> <br /> Nota : {{literal|git checkout -b me_mybranch}} is a shortcut for last two commands<br /> <br /> If it's a minor fix (typo / [https://en.wikipedia.org/wiki/Doxygen doxygen] [http://download.tuxfamily.org/synfig/api/index.html code documentation] / ... for example) you can do it from your origin master. But be aware that a nice name for {{literal|me_mybranch}} help the brain to work less ;-). It's also useful for the rest of the universe who take a look to [https://github.com/search?utf8=%E2%9C%93&amp;q=cat+simulator&amp;type=Repositories&amp;ref=searchresults your contributions]. <br /> <br /> So i starts coding in my bug fix, feature, test ... local branch and add has necessary commit and comments.<br /> $ git add my_files<br /> $ git commit -m ....<br /> <br /> And when i have finished, my local branch is updated.<br /> <br /> To synch local with upstream i should :<br /> $ git fetch upstream (update all branches in upstream)<br /> $ git checkout master<br /> $ git merge upstream/master | git rebase upstream/master<br /> <br /> So my local branch should be synchronized with original synfig repo (upstream). <br /> <br /> Just before sending to github, don't forget to check the final integration of your contribution and the actual master code still are stable. If things are well commented, all files commited ... <br /> <br /> Now i can update my forked repo on github (origin)<br /> $ git push origin me_mybranch<br /> <br /> Make a pull request on github. <br /> <br /> When the pull is accepted, it's time to update the [http://www.synfig.org/issues/thebuggenie/synfig tracker] and {{l|Category:Manual|documentation}} part of the project.</div>

D.j.a.y