What you don’t know about Git and GitHub
My initial encounter with git and GitHub was a little interesting. I thought the two were the same guy and never understood the idea that formed the technical background of the two.
In case you are another version of me trying to figure out the difference then consider this juxtaposition: the difference between git and GitHub corresponds to the difference between porn and Pornhub. While git is the software that runs GitHub, porn is the engine that runs Pornhub, such a punchline to a serious joke.
Git is an open source (free) software that eases the work of making changes and publishing consistent and more stable releases of applications. GitHub provides servers to host your application files, same to Gitlab.
Git has been a key stakeholder in the realm of Software development and particularly Software development life cycle, and has relatively experienced less exponential competition from other version controls such as the subversion.
One therefore gets the privilege of accessing both local and remote repositories using git, collaborating virtually and developing working workflows that favors the complexity of the project. Git offers a super cool compression algorithm for remotely uploading project files (beta compression), of course via the command line, cool.
The technology of version controls such as git has been integrated with other technologies to automate tasks leading to a new approach called Continuous Integration/ Continuous Development (CI/CD) commonly known as DevOps and this concept has been propagated to other fields such as the Manufacturing Industry.
Consumers are demanding for new product features more rapidly than software engineers can develop and release them, therefore continuous automated testing and releases is mandatory to maintain the relevancy of a product in the market.
The truth is, though inconvenient yet irrefutable, as a developer or someone working around applications development, you need a grasp of a relevant version control fundamentals, preferably git. Git commands are descriptive to what they do and a few of them does much, you will use few of them in your path as a developer, and it is interesting I tell you. The motivation is; START GITTING and KEEP GITTING.
Thanks for the time, next we will look at Git In Windows and Linux , the installation and every stuff before we get down to committing, pushing, pulling….Same place, same time.
