Overview of Git Git is a Version Control Management System (VCMS). The most popular use for it is to manage source code for software development projects but it can be used to manage any type of computer files. It was built initially to support development of Linux and focused on speed and scalability as it’s[…]
I’ve recently run across an interesting challenge in some historical source code repositories. These repositories did not begin their lives in Git and are arranged so that independent products are in sub-directories under a root parent directory. This means, any time anyone clones the repository they get a ton of unneeded source code that goes[…]
Git is my go to source control management tool. It works no matter what the technology or platform of the project I’m working on involves. I’ll be honest. It took a little brain power to understand when I first switched over to it to get a good grasp on it. When files disappear from a[…]
I ran into a new branching strategy, branch by sprint, this week. I will have to admit it was a new one to me. I’ve seen branching by environment (dev, test, staging, prod), branching by developer, and branching by feature/user story. I had not considered branching for a sprint. […]
My journey to a new Source Control Repository technology mastery is well under way. Recently I’ve made the leap from Team Foundation Source Control to Git. The move comes after much consideration on my part. Why change? Doesn’t Team Foundation Server do pretty much the same as Git? Is it really worth the upheaval to change everything over to a Git repository?
I struggled with all of these questions. Eventually I was won over by the undeniably huge acceptance of Git in both the open source and private development communities, the branching flexibility of Git, and the just downright speediness Git. […]