Github

Github is incredibly useful, but when the team working on a collaboration in a repository gets too large things get pretty ridiculous with commit conflicts - it's absolutely necessary to have a strict set of rules for who can edit what files when the team size gets that large. Or split the repository up into separate repositories for each part of the coding project, but that's not ideal sometimes.

That said, I use it all the time these days and its perfect for small groups and individual use :)

Also, you don't even need to learn the terminal commands for git these days - you can manipulate the files through the website (minus a few useful commands). Or, even further, if you use Visual Studio then you can use the github extension which is really cool - https://visualstudio.github.com/ - although this requires VS2015, but I can highly recommend it :)
 
Last edited:
PhysicsMan94 said:
Github is incredibly useful, but when the team working on a collaboration in a repository gets too large things get pretty ridiculous with commit conflicts - it's absolutely necessary to have a strict set of rules for who can edit what files when the team size gets that large.
Click to expand...

If that's an issue, sounds like the team needs to read up on separation of concerns or on multiple feature branches. Good code structure should reduce the amount of conflicts you get.
 
Well this thread went well :p


I have absolutely no idea what any of you lot are talking about but this looks like a very interesting venture so I'll probably start on it this afternoon.

Thanks for the help as always folks, it really is appreciated!
 
We keep hitting situations that would be helped with GIT at work when doing little scripting projects, but the projects are always so small that nobody can be bothered to invest the time in figuring it out. We keep getting told by the Microsoft guys that TFS will do it for us too?

We have a Powershell script that we use for automating backups and service restarts with logging and emailing, and its been a different version every time I've deployed it :p. I just ask the guy who wrote it for the latest copy and then ask him to fix it if it breaks :p.

Annoyingly the core software I consult in, which is a major product from Oracle, has zero source control on the code written elements of it and zero ability to easily integrate with an external one. It's a massive pain when all you have is the script in its current form, and occasionally a record of the last person to edit it.
 
Diddums said:
Well this thread went well :p


I have absolutely no idea what any of you lot are talking about but this looks like a very interesting venture so I'll probably start on it this afternoon.

Thanks for the help as always folks, it really is appreciated!
Click to expand...

Don't sweat it, Diddums. The art of tech: if you aren't confused, you're doing it wrong. :) For just learning to code a few simple scripts -- dropbox will do. But learning source control is valuable in the long run, especially if you want to contribute to open source projects later or work in larger teams on larger things.
 
Skeeter said:
We keep getting told by the Microsoft guys that TFS will do it for us too?
Click to expand...

I think the fact that Microsoft are now heavily investing in Git and using github to host .NET core and related frameworks, Git is much more futureproof and widely adopted than TFS.
 
Just make sure you setup your gitignore properly, because one day you'll clone a project to find someone accidently dropped a 400mb sql dump into the repository.

Ah, the fun I had trying to figure out how to purge that from the records the first time it happened.
 
We use Mercurial (hg) at work. I chose it back when 50% of people used Git and 50% of people used Mercurial. I think within the first week of joining the company I started migrating us away from Sourcegear Vault which was way too painful to use.

I still find it much better than Git, and TortoiseHG is so much better than TortoiseSVN, TortoiseGIT or sourcetree etc but it seems every other developer thinks differently now :p
 
Last edited:
I've just started using GitHub for a project and find it completely confusing. Some of the explanations here have finally helped explain to me what it's actually for. I figured if you come from a programming background and have always worked with these sorts of tools then it was probably quite obvious, but for outsiders it's way confusing :p
 
I use GIT through visual studio, and while there are some features it doesn't support via the GUI, it does simplify the majority of day-to-day tasks.

GIT is a very good VCS, but it's popularity is a bit faddy, as are lots of things in the development community. TFS is still very good for the majority of dev teams.
 
You must log in or register to reply here.
Back
Top Bottom