Version Control

[A Former User]

@orange @d-healey has a nice video that'll get you started. https://youtu.be/Bs3zI5Dtvn0
You'll find lots of resources online actually... I am using git as well and am just testing the desktop app. I hear that sworn professionals don't like the app and prefer the terminal access (macOS) but I quite like it tbh. But I am definitely not an expert in this! But I am sure we have those experts in our midst!

[Christoph Hart]

I‘m using sourcetree, which works fine on all platforms.

[orange]

@UrsBollhalder Thanks, I watched this David's great tutorial before. But this usage is based on "Terminal". I asked for without using Git's Terminal stuff ;)

[orange]

@Christoph-Hart said in Version Control:

I‘m using sourcetree, which works fine on all platforms.

Looks interesting, Thanks I will check it out.

[ustk]

@orange I'm using GitHub Desktop, I like it.

[orange]

@ustk said in Version Control:

@orange I'm using GitHub Desktop, I like it.

Yeah it's great also, much more user friendly than Git's Terminal stuff :)

[d.healey]

You don't need different branches for each version - depending on what you mean by "version". Generally you have a single continuous master branch and you make separate branches for different features you're working on, when the feature is complete you merge it into the master branch. When it's at a stage that you want to give a version number to you can "tag" the current commit in the master branch as a release. If you click on the tags link in the HISE repo you'll see the tagged releases for example.

[orange]

@d-healey Very informative as always, Thank you.

[hisefilo]

@d-healey thanks David for the guidance. Same here. The only issue is thar merging still being a complex tax for me. I have to confess returning to Master is almost impossible for mr at this point :)

[d.healey]

@hisefilo Make a test project with a text file in it to practice.

[hisefilo]

@d-healey will do!!!