Why Git cannot be HEADless

Any software developer is bound to come across this amazing thing called Git at some point, especially if they are working on team projects.But just what is Git? And why do we love it so much? What is the fuss around the HEAD in Git? I’ll try to answer this from my point of view.

It was at the Andela boot-camp that I first came across Git when we were introduced to version control. Fortunately for me, this was one of the concepts I took to rather quickly. Not that I’m an expert, no one can be after using something only a few times, but I have come to appreciate the use of Git as a means of tracking changes in a project being undertaken step by step. So yeah, that is basically what Git does in layman terms, enable you to track changes. Simple yet effective.

One of the most important aspects in Git is the HEAD. Described as the reference to the node to which the working space in the repository points, the head acts like a sort of address pointing towards a certain commit. This makes the head a very important piece in version control as it helps identify individual commits and may also be used to check differences between these commits. That said, the head, much like your very own head, is a vital center piece in the entire version control process in Git.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.