With my GMS2 projects, I personally use; - Sourcetree - Bitbucket Plenty of free functionality for hobby users, by far the easiest way to backup and share source code via the cloud. I dare say Bitbucket vs Github are more or less the same, but would be curious of any feature comparison against the two.
I just wish there was better build in support for git in GMS. I've heard horror stories about the sheer number of conflicts that occur when working in a team. But for solo devs, I agree, source control is a no brainer.
For versions of GameMaker before 2.3 I believe there were and still are a couple of game corruption issues that could occur when merging substantially different branches. My understanding is that 2.3 has fixed those entirely although I've run into a couple minor annoyances with the current beta.
I have used Github Desktop, and thought it was pretty nice, but I personally prefer the command line for teaching for a couple reasons. First, it doesn't actually require Github. And while Github is certainly amazing and what I use, not everyone does. Second, it blurs the line between Git and Github which are not (as you know) the same thing. But the big reason is that 100% of what Git does is available from the command line which, and the vast majority of resources for Git (such as the free manual), us it, so understanding how to use and read the command line is the most useful for learning in my opinion because if you run into a problem you have a wider space to find an answer. That said, if you do understand git already, and you know your workflow is entirely covered by Github Desktop, then it is a great option especially since it integrates Git and Github which is what almost everyone is going to want. So I'm certainly not trying to persuade anyone not to use Github Desktop. Maybe I'll do a video on some of the various GUI tools at some point.
@@SamSpadeGameDev absolutely. My biggest barrier when learning Git was strangely enough, not realising that Git and Github were two different parts of the puzzle. 😂
@@SamSpadeGameDev My biggest issue with Git alone through GM was I couldn't reliably get it to function and frankly the documentation explaining was super hard to find. I am glad your addressing it because it makes collaboration so much easier within teams!
Instead of Google Docs, I would've gone with Wikipedia (and any other wiki) myself. $:^ ] In fact, ha ha ha, I didn't even know Google Docs had the archival ability as such. $:^ P
With my GMS2 projects, I personally use;
- Sourcetree
- Bitbucket
Plenty of free functionality for hobby users, by far the easiest way to backup and share source code via the cloud. I dare say Bitbucket vs Github are more or less the same, but would be curious of any feature comparison against the two.
I just wish there was better build in support for git in GMS.
I've heard horror stories about the sheer number of conflicts that occur when working in a team.
But for solo devs, I agree, source control is a no brainer.
Incredibly true. My buddy and I ended up going with Github Desktop.
For versions of GameMaker before 2.3 I believe there were and still are a couple of game corruption issues that could occur when merging substantially different branches. My understanding is that 2.3 has fixed those entirely although I've run into a couple minor annoyances with the current beta.
Hey Sam, not sure if you ever considered trying out Github Desktop, but its an super alternative to bash and having a GUI makes it real user friendly.
I have used Github Desktop, and thought it was pretty nice, but I personally prefer the command line for teaching for a couple reasons. First, it doesn't actually require Github. And while Github is certainly amazing and what I use, not everyone does. Second, it blurs the line between Git and Github which are not (as you know) the same thing. But the big reason is that 100% of what Git does is available from the command line which, and the vast majority of resources for Git (such as the free manual), us it, so understanding how to use and read the command line is the most useful for learning in my opinion because if you run into a problem you have a wider space to find an answer.
That said, if you do understand git already, and you know your workflow is entirely covered by Github Desktop, then it is a great option especially since it integrates Git and Github which is what almost everyone is going to want. So I'm certainly not trying to persuade anyone not to use Github Desktop. Maybe I'll do a video on some of the various GUI tools at some point.
@@SamSpadeGameDev absolutely. My biggest barrier when learning Git was strangely enough, not realising that Git and Github were two different parts of the puzzle. 😂
@@SamSpadeGameDev My biggest issue with Git alone through GM was I couldn't reliably get it to function and frankly the documentation explaining was super hard to find. I am glad your addressing it because it makes collaboration so much easier within teams!
Instead of Google Docs, I would've gone with Wikipedia (and any other wiki) myself. $:^ ]
In fact, ha ha ha, I didn't even know Google Docs had the archival ability as such. $:^ P