Getting Started with Git and GitHub in VS Code – A Beginner’s Walkthrough

What’s happening?

GitHub just released a new tutorial series called GitHub for Beginners. The latest episode, presented by Developer Advocate Kedasha Kerr, walks newcomers through the full Git workflow inside Visual Studio Code (VS Code). The article covers everything from creating a repository on your local machine to publishing it on GitHub, merging branches, and even using the Model Context Protocol (MCP) extension to let Copilot call external tools.

Why developers should care

Most of us spend at least a few minutes each day switching between a code editor, a terminal, and a browser‑based GitHub view. Those context switches add friction, especially for people who are still learning the basics of version control. VS Code ships with built‑in Git support, so you can perform the entire Git lifecycle without leaving the editor. That means:

• Faster feedback loops because you see changes, diffs and branch status right next to your code.
• Fewer accidental mistakes caused by copying commands between windows.
• A smoother onboarding experience for newcomers who might be intimidated by the command line.

The guide also highlights how the new GitHub MCP extension lets AI tools like Copilot safely interact with external services, opening the door to more sophisticated, AI‑driven workflows.

Walk‑through of the tutorial

1. Install the prerequisites

• Git – the version‑control engine. If you missed the earlier episode, you can follow the install instructions on the Git website.
• VS Code – download it from the official page.
• (Optional) GitHub Copilot – for AI‑generated commit messages and code suggestions.

2. Initialise a folder as a repository

1. Open VS Code and click the Explorer icon on the left.
2. Choose Open Folder and select the directory that contains your project.
3. Click the Source Control icon (third from the top) and hit Initialize Repository.
4. You’ll see the branch name (default main) appear in the bottom‑left status bar.
5. To rename the branch, open the Command Palette (Shift+Cmd+P on macOS or Ctrl+Shift+P on Windows) and run Git: Rename Branch.

3. Stage, commit and push changes

• Files appear with a U (untracked) next to them. Click the + icon beside a file or the + next to CHANGES to stage everything. Staged files show an A.
• Type a commit message in the text box at the top of the Source Control pane. You can click the Copilot icon to let the AI suggest a message.
• Press Commit. The changes are now recorded locally.
• To push to GitHub, click Publish Branch and choose public or private. VS Code will create the remote repo and push the commit in one step.

4. Working with branches

Creating a new branch is as simple as opening the Command Palette, typing create branch, and providing a name (e.g., new‑features). VS Code automatically switches you to the new branch. The bottom‑left corner updates to show the active branch.

5. Seeing what you changed

• Gutter indicators: a thin green line for added lines, a blue patterned line for modifications, and a red arrow for deletions.
• Diff view: click a file under CHANGES to open a side‑by‑side comparison. Use the three‑dot menu in the diff view to switch to Inline View, where you can edit directly inside the diff.

6. Merging back to main

1. Switch back to main via the branch selector in the status bar.
2. Open the three‑dot menu next to CHANGES, hover Branch, then choose Merge….
3. Pick the feature branch you want to merge. VS Code will apply the changes and update the UI.

7. Cloning an existing repository

1. On GitHub, click the Code button and copy the repository URL.
2. In VS Code, open the Command Palette and run Git: Clone.
3. Paste the URL, pick a local folder, and let VS Code open the cloned repo.

8. Extending the workflow with Model Context Protocol

The GitHub MCP extension lets Copilot invoke external tools safely. To install:

• Open the Extensions view, search for @mcp github, and click Install.
• Authorise the MCP server when prompted.
• After installation, you can open Copilot Chat, ask it to create issues, generate code, or run other actions that require external data.

For a video demonstration, check out the episode on the GitHub for Beginners YouTube playlist.

Community reaction

Since the article went live, the comment thread on the blog post has been buzzing. New developers appreciate the “no terminal needed” angle, while seasoned contributors like the MCP section for its potential to automate repetitive tasks. On Hacker News, the post gathered a handful of up‑votes and a discussion about whether AI‑assisted Git operations could eventually replace manual review steps. The consensus: the tutorial is a solid entry point, but teams should still enforce code‑review policies before merging.

Takeaways

• VS Code’s built‑in Git UI lets you perform the entire version‑control cycle without leaving the editor.
• Branching, staging, committing and publishing are all a few clicks away, which lowers the barrier for newcomers.
• The Model Context Protocol extension demonstrates how AI can be integrated safely into the workflow, hinting at future productivity boosts.

Give the guide a try, experiment with the MCP extension, and share your experience on the #vscode‑git channel in the GitHub Community Forum. Happy coding!