Daniel,
Git is super easy once you get the hang of it. You will clone your own copy
of the repo in github and make updates to your own branches in it. Then
when you are ready to merge back to the production MS repo, you create a
pull request in github.
Git encourages profligate branching because it is so good at merging. I
recommend making a branch for anything you do. You might also want to get
SourceTree, which gives you a nice gui on top of git. It will show you the
branch history, and that may help you visualize how it works.
On Fri, Dec 30, 2016 at 6:13 PM, oberon <[email protected]> wrote:
> Hi Daniel!
> You will need to read up on branches and on upstream syncing.
> You'll find tons of information on the Github help pages, on stackoverflow
> and similar pages. git might seems a bit intimidating in the beginning but
> it's really a wonderful tool!
>
> Have fun! :)
>
>
>
> --
> View this message in context: http://dev-list.musescore.org/
> github-and-version-control-tp7580093p7580094.html
> Sent from the MuseScore Developer mailing list archive at Nabble.com.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Mscore-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
