Just like any house requires a foundation or any chemical reaction requires individual elements, I realized coding requires an elaborate understanding of the version control system. My Git project was intentionally designed as a progressive journey into the world of version control and collaboration. Initially I could type commands in my terminal without necessarily being sure what they do, I quickly discovered this was not sustainable. I now have to unlearn, learn and relearn if I am to stand any chance in this field.
The project laid down the basics of what I need, starting from git init, a command to create a git repository to git push, one to send my project to the repository. I moved from ground up, git clone, a command to pull down project templates into my terminal, the staging cycle where my code moves between states. The three states of Git have become an integral part of my journey as everything coding is done here. The working directory comprises my active code files, the staging area, git add . & git commit -m and the repository, _git push _.
I hit this puzzle that required me to stage once but commit twice, and that's how I learnt git add -p , a command that allows me to commit sections of my file separately. Moving through the project taught me this deep web of commands that would become integral in group collaboration such as git switch -c, git log, git push origin (branch name), etc.
At the end of the project, my git skills progressed from frantic guesswork to deliberate, structural control. Indeed, git is not just a list of terminal prompts to memorize, it is a logical environment built to protect my work. Another week, another reason to look forward for more.
Top comments (0)