Skip to content

Refresh Your Git Skills

Glossary

Git A version control system that tracks changes in your project so you can work safely, undo mistakes, and collaborate with others.

Repository (repo) A project folder that Git manages. It contains your files and the full history of changes.

Branch A separate line of development where you can work on features or fixes without affecting the main project.

Main / Master The primary, stable branch of the project. Most teams treat this as the "official" version of the code.

Commit A saved snapshot of your work. Each commit includes a message explaining what changed and why.

Merge Combining changes from one branch into another. This is how your work gets integrated back into the main project.

Merge Conflict When Git can't automatically combine changes because both versions edited the same part of a file. You must decide how to resolve it.

Push Uploading your local commits to the remote repository.

Pull Downloading the latest changes from the remote repository to your local machine.

Clone Making a full local copy of a remote repository so you can work on it.

Fork Creating your own independent copy of someone else's repository, usually to propose changes or start your own version.

Pull Request (PR) A request for teammates to review your changes before merging them into the main branch.

Commit History A chronological list of all commits. Useful for reviewing past decisions, debugging, or understanding how the project evolved.

Even though you’ve already learned Git in earlier courses, it’s completely normal to feel a bit rusty when you start using it in a real project. In this course Git is your team’s lifeline: it keeps your work safe, keeps your history clean, and helps you collaborate without stepping on each other’s toes. If you want to warm up your basics — branching, merging, rebasing, staging, resolving conflicts — the resources below are great practice. Think of them as a quick “muscle memory reboot” before the real teamwork begins.

The links offer different styles: interactive games, visual explanations, official documentation, and short videos. Try one or two that fit your learning style — you don’t need to master everything, just rebuild confidence so you can work smoothly with your team.

Tip

Practicing Git before the project gets intense will save you hours later. A calm 20-minute refresher now often prevents messy conflicts during milestone weeks.

If you already feel confident, great — keep going. If not, take a moment to rebuild your foundation. Your future self (and your teammates) will thank you.