Why VCS-Version Control System Exists ?
B.Tech student at NIT Jalandhar, currently learning web development and actively upskilling in frontend fundamentals. Exploring HTML, browser behavior, and how the web works behind the scenes, with a focus on building strong basics. I believe in consistent learning, understanding systems deeply, and improving step by step. Documenting my journey, building projects, and growing toward tech-driven roles through hands-on practice 🚀
Imagine you’re building a project and saving it on a pendrive.
Day 1 you save project_final.
Day 2 you make changes and save project_final_v2.
Day 3 something breaks, so you copy project_final_v2_backup.
Now your pen-drive is full of confusing files, you don’t know which one works, and if the pen-drive gets lost or corrupted, everything is gone.
A Version Control System (like Git) solves this.
Instead of copying folders again and again, it records every change, lets you go back to any previous version, shows who changed what, and keeps your project safely stored in multiple places.So instead of carrying a risky pen-drive with messy versions, VCS gives you a clean history, backups, and teamwork—without the chaos.
Before Version Control Systems (VCS), developers managed code manually, which caused many problems:
Multiple copies like final, final_v2, final_really_final
No way to know who changed what and when
Hard to go back if a feature broke
Team members overwriting each other’s work
Code stored locally → risk of data loss
Sharing code via pen-drives, emails, or zip files
Managing projects became messy, slow, and error-prone.
Git is a distributed version control system whereas git-hub acts as a server where all the coders can collaborate and write their code without any fear of clashing.
Key things Git does:
Tracks code changes locally
Allows branching and merging
Works offline
Keeps full project history on your machine
Git helps you experiment freely without fear of breaking your project.
Introduction to GitHub
GitHub is a cloud platform that hosts Git repositories.
GitHub allows you to:
Store code online
Collaborate with teams
Share projects publicly
Track issues and pull requests
Build a developer portfolio
This diagram shows how Git and GitHub work together in the real world. Everything starts on your local machine. You create or modify files inside your project folder (working directory). When you’re ready to save changes, you add those files to the Git staging area, which acts like a preparation zone. Once staged, you commit the changes, and Git stores a snapshot in your local repository.
Your local repository lives only on your computer. To share your work or back it up online, you push these commits to the GitHub repository, which lives in the cloud. GitHub now becomes the central place where code is stored and shared. If changes are made on GitHub—either by teammates or through the web interface—you can pull those updates back into your local repository to stay in sync.
The diagram also shows that GitHub allows direct commits through its web interface, but Git is still running behind the scenes. Git tracks every change locally, while GitHub acts as the remote hub that connects developers, enables collaboration, and keeps projects safe.