My Git & GitHub Journey
When I started learning Git and GitHub, I mixed them up. I thought they were the same thing. I learned that Git is the version control tool on my computer, and GitHub is the online platform where I store and share repositories.
At first, the commands felt like a foreign language. I didn’t understand why I needed to git add and then git commit before I could git push. Branches confused me even more, and I wasn’t sure why I would work on a separate branch instead of just editing main.
Practice made things clearer:
The staging area makes sense now.
git addchooses what goes into a snapshot, andgit commitsaves it with a message.Commit messages matter. I learned to write meaningful ones so my history tells a clear story.
Branches are safe spaces. Creating a branch like
fintech-modulelets me experiment without touchingmain.Conflicts aren’t scary. My first merge conflict looked like a disaster. I learned it just means two branches changed the same lines, and I get to choose the final version.
Pulling keeps me in sync.
git pullbrings GitHub changes into my local copy, so I stopped getting rejected pushes.
I still have more to learn, like rebasing and pull request reviews, but I’m much more confident than when I started. Git and GitHub now feel like tools that protect my work instead of confusing me.