Learn Git & GitHub Desktop in 5 Simple Steps
Master version control the easy way with GitHub Desktop | Coding Blocks

Imagine this: You’ve just written some killer code for your college project, or maybe you’re building your first full-stack app. But suddenly, something breaks. You try to undo your changes… and now your entire project is gone. Sounds familiar?

That’s exactly why developers use Git, a version control system that tracks every change made to your code, lets you roll back to earlier versions, collaborate with others, and keep everything organized. And while Git is incredibly powerful, it can feel intimidating, especially if you’re not comfortable with the command line.

Enter GitHub Desktop, a beginner-friendly, graphical interface that removes the fear of version control. With a simple UI and seamless GitHub integration, it allows you to create repositories, push code, handle branches, and collaborate with others without writing a single terminal command.

At Coding Blocks, we believe every developer, beginner or expert, should be fluent in version control. Whether you’re aiming for top internships, freelance work, or industry placements, Git is a must-have skill in your toolkit.

This guide walks you through 5 essential steps to get started with Git and GitHub Desktop, with practical actions, real context, and future-ready workflows.

Step 1: Create Your Repository Locally and on GitHub

Every Git journey starts with a repository. A repository is like a digital folder where all your project files, changes, and version history are stored. You can create one locally on your system, and then publish it on GitHub so it’s backed up online and ready for collaboration.

Open GitHub Desktop and click on File > Add Local Repository. Choose the folder where your project lives, maybe it’s your first JavaScript project, a C++ DSA template, or a React app, and click Add Repository.

Next, it’s time to go live. Click the Publish repository button. You’ll be prompted to name your repository (choose something descriptive), add a brief description (like “My portfolio site” or “DSA template”), and set visibility to public or private depending on your need.

Start by creating a project folder on your machine. Open GitHub Desktop and follow these steps:

Create Your Repository Locally and on GitHub
  1. Add Local Repository:
    Go to File > Add Local Repository, select your project folder, and click Add Repository.
  2. Publish to GitHub:
    Click the Publish repository button, set your repository name and description, choose whether it’s public or private, and hit Publish.
Create Your Repository Locally and on GitHub

If you’re part of a GitHub organization (like a Coding Blocks classroom), you can choose where to host it. Otherwise, it’ll be under your personal account.
Once published, you have a two-way bridge between your local machine and GitHub’s cloud servers. You’ve officially versioned your project.

Step 2: Push Local Changes to GitHub

You’ve created your repository. Now comes the part you’ll repeat often, making changes, saving them, and pushing them to GitHub.

As you build your project, GitHub Desktop constantly monitors your changes, whether you’re adding new files, updating scripts, or tweaking HTML and CSS.

Whenever you're ready to save progress:

Stage Changes: GitHub Desktop automatically stages modified files. You can select/deselect them if neede

Push Local Changes to GitHub

2. Commit Changes: Write a clear message like “Added login feature” or “Fixed navbar bug”, this makes tracking your progress easier. Then click Commit to main.

3. Push Changes: After committing, click Push origin to upload your changes to GitHub. This syncs your local repo with the online one.

Push Local Changes to GitHub

This system ensures every meaningful change is saved and traceable. If something breaks, you can always roll back.
And if your team members are working on the same project, they can see your commits in real time, pull the updates, and stay aligned.

Step 3: Clone and Pull Repositories

Sometimes you won’t start a project from scratch. Maybe you’re joining a team, contributing to open-source, or trying out a project someone shared. That’s where cloning comes in.

Clone and Pull Repositories

To clone a repo:

  1. Visit the GitHub repository page.
  2. Click Code > Open with GitHub Desktop.
  3. Select a local folder to save it, done.

You now have a full copy of that project, complete with its version history, on your computer.

Clone and Pull Repositories

But cloning is just the beginning. Repos evolve, new features are added, bugs are fixed, and you’ll need to stay updated. That’s where pulling comes in.
Whenever someone else makes changes to the remote repo, you can click Fetch origin in GitHub Desktop. This brings in their latest changes without overwriting your own.

And if there are updates, clicking Pull origin merges those updates into your local version.

💡 Pro Tip: Always pull the latest code before starting your own changes. This prevents conflicts and ensures you’re working on the most recent version.

This pull/clone mechanism is crucial for teamwork and for syncing with public repositories like those in Coding Blocks' GitHub classroom exercises or open-source programs.

Step 4: Branching, Pull Requests & Merging

Collaboration is the heart of modern development, and Git branches make it possible.
A branch lets you create a separate workspace within your project, perfect for adding new features, fixing bugs, or experimenting safely. Your main branch remains untouched while you work.

In GitHub Desktop:

  1. Click Current Branch > New Branch and give it a name like feature/contact-form or fix/navbar-bug.
  2. Work freely in this branch, commit and push changes as usual.
Branching, Pull Requests & Merging

Once done, it’s time to bring your work back to the main project via a pull request (PR). This is Git’s official way to propose, review, and merge changes.

Branching, Pull Requests & Merging

To create a PR:

  1. Click Create Pull Request in GitHub Desktop.
  2. On GitHub, add a description, reviewers, and any related issue tags.
Branching, Pull Requests & Merging

Once reviewed and approved, the PR can be merged into the main branch.
This flow ensures your code is reviewed, bugs are caught early, and collaboration becomes structured.

💡 Best Practice: Never work directly on the main branch. Always create branches for features or fixes.

At Coding Blocks, this PR-based workflow is taught as part of our full-stack and DSA programs, because it mirrors how real teams work at Google, Microsoft, and Amazon.

Step 5: Optional – Install Git Credential Helper

If you’re using GitHub often, typing your username and password each time you push code can get annoying, not to mention insecure.
Thankfully, GitHub Desktop supports Git Credential Manager, which securely saves your login credentials. Once installed, you won’t be asked to log in again for every push or pull.

To install on Windows:

Visit: https://github.com/GitCredentialManager/git-credential-manager

Download and install the latest version.
GitHub Desktop will now authenticate seamlessly in the background.

💡 Note: GitHub now uses personal access tokens instead of passwords, and the Credential Manager handles these securely.

If you're working in professional environments, this becomes essential for safe, smooth collaboration.

Why You Should Learn Git Now

Git isn’t just a tool, it’s a developer's second brain.

Whether you're a college student, a freelancer, or preparing for placements, knowing Git gives you an instant edge. It shows employers you can collaborate, manage your work, and contribute to real-world projects.

Here’s why learning Git now pays off:

🔁 Undo mistakes without panic
💻 Collaborate on group projects efficiently
🚀 Contribute to open source with confidence
🧠 Track your coding journey like a professional

Every job-ready developer knows Git. It’s used by teams at Google, Microsoft, startups, and even Coding Blocks’ engineering team. In fact, Git knowledge is often assumed in interviews — especially in system design, web dev, and full-stack roles.

With GitHub Desktop, there’s no excuse to delay. You can skip the terminal anxiety and start managing code like a pro, visually.

💡 Remember: you don’t need to learn everything today. Start small. Push a personal project. Create a branch. Merge a pull request.

The earlier you begin, the sooner Git becomes second nature.

Master Git with Coding Blocks

At Coding Blocks, we don't just teach you to code, we teach you how to manage, collaborate, and ship production-grade software.

Git and GitHub are baked into our curriculum:

✅ Build full-stack projects with Git-based versioning
✅ Collaborate on group assignments using pull requests
✅ Submit classroom tasks using GitHub Classroom
✅ Prepare for job-ready Git workflows used in top tech firms

Explore our flagship programs:

  1. Full Stack Web Development (MERN)
  2. Master Data Structures & Algorithms (Java, C++, Python)

Learn version control the right way, in real projects, with real mentors.

👉 Browse all Coding Blocks Courses

Final Thoughts

Git is your foundation as a developer, and GitHub Desktop makes it easy. With simple steps like creating repos, pushing changes, and opening pull requests, you’re already on the path to pro-level workflows. Coding Blocks is here to make it practical, real, and job-ready.

Version control isn’t optional anymore it’s the language of modern development. GitHub Desktop lowers the entry barrier, helping you skip terminal confusion and focus on building great software. Whether you're coding solo, collaborating with classmates, or aiming for internships at tech giants, Git fluency will always set you apart. So don’t wait. Install GitHub Desktop, push your first commit, and experience the power of clean, trackable, collaborative code.

And when you’re ready to take your skills to the next level, Coding Blocks is right here with structured learning, real projects, and a path to your dream job.