Git Practice - Learn Git Interactively

Understanding Branch Structure and Switching

The project has multiple branches. You need to understand how to view them, switch between them, and understand what HEAD means.

#scenario-1-3

Initializing a New Repository

You are starting a brand new project. The first step is to initialize a Git repository to start tracking your files.

#scenario-1-4

Creating a Good Commit History

A clean, readable commit history is crucial for collaboration. Practice making small, logical, 'atomic' commits with clear messages.

#scenario-1-5

Discard Changes and Restore Files

You made changes to several files but want to discard them. Learn safe ways to undo uncommitted work.

#scenario-2-1

Temporarily Save Work with Git Stash

You're working on a feature when a critical bug needs immediate attention. Use stash to temporarily save your work so you can switch contexts.

#scenario-2-2

Viewing Changes with Diff and Log

Learn to inspect your code changes and commit history effectively using git diff and git log.

#scenario-2-3

Comparing Branches and Commits

Before merging or rebasing, you need to see what changes exist between branches. Learn to compare effectively.

#scenario-2-4

Connect to Remote and Push Changes

Your local project is ready. Now it's time to connect it to a remote repository on a service like GitHub to back it up and collaborate with others.

#scenario-2-5

Managing .gitignore Patterns

Learn to properly configure .gitignore to exclude files you don't want to track, and how to handle files that were accidentally committed.

#scenario-3-1

Branch Management Essentials

Master creating, switching, renaming, and deleting branches - the most frequent Git operations in daily development.

#scenario-3-2

Feature Branch Workflow

The standard workflow for developing a new feature is to create a dedicated branch. This keeps the 'main' branch clean and allows for code reviews before merging.

#scenario-3-3

Keep Your Branch Updated with Rebase

Your feature branch was created yesterday. Today, main has several new commits. Use rebase to build your feature on top of the latest main, keeping a clean linear history.

#scenario-3-4

Pull Remote Updates with Rebase

You have local commits on main, but a teammate pushed new commits to origin/main. Use git pull --rebase to avoid unnecessary merge commits.

#scenario-3-5

Resolving Merge Conflicts

You've been working on a feature, and in the meantime, someone else changed the same line of code on the 'main' branch. It's time to merge, and you need to resolve the conflict.

#scenario-4-1

Fork Workflow and Creating Pull Requests

You want to contribute to an open-source project. Learn the fork workflow: create your own copy, make changes, and submit a pull request.

#scenario-4-2

Squash Commits Before Pull Request

Your feature branch has messy commit history: 'WIP', 'fix typo', 'actually fix it'. Before submitting a PR, clean it up by squashing commits into one logical change.

#scenario-4-3

Code Review Workflow and Amending Commits

After pushing your feature branch, a reviewer requests changes. Learn to amend your commit and update the pull request.

#scenario-4-4