git — the stupid content tracker

Git has a lot to offer, sometimes is overwhelming, for that reason it’s good to have a practical approach and explanations along the way to grasp the essentials of this magnificent tool.

This is the first part of a series of articles to introduce you to Git and then to level up your working development workflow using git.

Content.

Git history (brief).
Git workflow.
Hands-on Git.
Git history (brief)
git — the stupid content tracker
man page
The problem
A software is a piece of code that grows, in every new feature added a tag is placed in it and you get new versions. Eventually, the owner needs to share that code and allow contributions from other people to make that software better (or worst…). How to achieve this? for the first part, the answer is: Version Control System (VCS) to track the changes. For the second part we have two possible answers:

having a centralized system that keeps track of all the changes in your code.
having a distributed system where all the code is shared among contributors that work merging changes.
So, what Git is? is a Distributed Version Control System

Brief History
In April 2005, Linus Torvalds was working on the 2.6.12 version of his Linux operating system, not pleased with the current VCS available in the market to help him manage his code (BitKeeper as the main one), he decided that he needed to create it’s own to keep track of changes of the Linux core. This system had to be:

Distributed
Fast
Reliable
And… he did it. Git was created. Since then it has been growing almost universally to manage version control and team contributions.

For the sake of brevity, these are the main things to know.

#git #basic definitions #tutorials #command collections #tips collections