Interactive roadmap
Git and GitHub for Absolute Beginners roadmap
Perfect for absolute beginners, this friendly roadmap teaches you how to track your code changes and share projects online using Git and GitHub with confidence.
- 1
Why Version Control
0 of 3 done
Understand the core concepts of tracking changes in your code.
Take your time with these early steps; setting solid foundations makes learning Git much easier later on. - 2
Your First Repository
0 of 2 done
Create your very first local project folder tracked by Git.
Always check that you are inside the correct project folder before running any Git commands. - 3
Saving Work With Commits
0 of 2 done
Learn how to capture permanent snapshots of your work.
Write clear commit messages so your future self can easily understand what changes you made. - 4
Connecting to GitHub
0 of 2 done
Back up your local project safely on the internet using GitHub.
Treat your GitHub profile like a professional portfolio where your best coding journey is on display. - 5
Branches and Pull Requests
0 of 2 done
Work on new ideas safely and share them with others.
Always create a new branch when trying out an experiment so your main project stays clean and safe.
Learn it all, with a tutor that never sleeps
Every topic links to LevelUp lessons, practice exercises and the 24/7 AI Tutor. Your progress updates as you master lessons.
Every topic explained
Step 1: Why Version Control
- Git is a tool that saves the history of your files so you can step back in time whenever you make a mistake.Git Documentation
Read more
Git is a tool that saves the history of your files so you can step back in time whenever you make a mistake. Think of it like a video game save system for your writing or code, letting you experiment freely.
Imagine you are writing a recipe book and want to try a new cake topping. Instead of risking your original recipe, you make a backup copy first. Git does this automatically for every line of code you write.
This matters because it removes the fear of breaking things. You can always undo mistakes and see exactly what changed over time.
- Saves history of your files
- Acts like a safety net
- Lets you undo mistakes easily
- Tracks every change you make
- Get Git set up on your computer so you can start using it right away from your command line.
Read more
Getting Git set up on your computer lets you start using it right away from your command line. It is the engine that powers all your future version control tasks.
Just like installing a web browser to view websites, installing Git gives your computer the special software it needs to track file histories locally.
This step is essential because without the software installed, your computer will not understand any of the commands needed to run Git.
- Downloads the Git software
- Enables command line usage
- Prepares your local computer
- (optional)
- Learn a few simple text commands to navigate your computer folders and talk to Git.
Read more
Learning a few simple text commands helps you navigate your computer folders and talk to Git. Instead of clicking around with a mouse, you type short instructions.
Think of the terminal like talking directly to your computer. Typing cd lets you change folders, while ls shows what files are inside them.
Mastering these basics is vital because Git relies entirely on the terminal for you to give it instructions and manage your projects.
- Uses text instead of clicks
- Navigates computer folders easily
- Commands include cd and ls
- Connects you directly to Git
Step 2: Your First Repository
- Turn any ordinary folder on your computer into a special Git project folder ready for tracking.
Read more
Turning any ordinary folder on your computer into a special Git project folder gets it ready for tracking. This tells Git to start paying attention to everything inside.
Imagine placing a special tracker box inside a cardboard storage box. From that moment on, every item you add or change inside is monitored.
This matters because Git only tracks projects that have been initialised as a repository, turning a normal folder into a version-controlled workspace.
- Turns normal folders into Git projects
- Initialises tracking capabilities
- Creates a hidden Git folder
- Ask Git to show you which files have changed and what is happening in your project right now.
Read more
Asking Git to show you which files have changed lets you see what is happening in your project right now. It acts as your dashboard for current activity.
Picture looking at a shopping list to see which items are still in your basket and which ones you have already paid for. Git status tells you your current project state.
Checking status regularly is a great habit because it ensures you always know what modifications you have made before saving them.
- Shows current project activity
- Lists changed or untracked files
- Acts as your project dashboard
- Prevents accidental oversights
Step 3: Saving Work With Commits
- Select which specific file changes you want to include in your next saved snapshot.
Read more
Selecting which specific file changes you want to include in your next saved snapshot is called staging. It lets you bundle related edits together.
Think of packing a suitcase before a trip. You gather the exact outfits you want to bring and place them on the bed before zipping them into the bag.
This matters because it gives you control over your save history, allowing you to separate different ideas into neat, organised packages.
- Prepares changes for saving
- Bundles related edits together
- Uses the add command
- Gives you control over history
- Save your staged changes permanently with a short note describing what you did.
Read more
Saving your staged changes permanently with a short note describing what you did creates a clear project history. Each commit is a permanent milestone.
Imagine taking a photograph of a painting at the end of every art class, writing a sticky note on the back explaining what you painted today.
Good commits are essential because they let you and others look back through time to see how the project evolved step by step.
- Creates permanent save points
- Requires a descriptive note
- Marks project milestones
- Uses the commit command
Step 4: Connecting to GitHub
- Create your free online account to store your code projects and share them with the world.
Read more
Creating your free online account allows you to store your code projects and share them with the world. GitHub acts as a cloud storage hub for Git repositories.
Think of it like setting up a cloud drive account where you can back up your phone photos so they are safe even if your device breaks.
This step matters because it bridges the gap between working locally on your computer and collaborating with other developers online.
- Provides online cloud storage
- Enables project sharing
- Acts as a developer portfolio
- Free to set up
- Upload your local commits up to GitHub so your work is safely stored online.
Read more
Uploading your local commits up to GitHub ensures your work is safely stored online. It copies your local save history to the cloud.
Imagine syncing your local music playlist to your online streaming profile so you can access your favourite songs from any device.
Pushing code is crucial because it creates a secure remote backup and lets others view or contribute to your projects.
- Copies local saves online
- Creates secure cloud backups
- Uses the push command
- Connects local and remote projects
Step 5: Branches and Pull Requests
- Create a separate workspace to try out new ideas without breaking your main working code.
Read more
Creating a separate workspace lets you try out new ideas without breaking your main working code. It is like having a sandbox for experimentation.
Imagine a chef preparing a new menu item in the test kitchen before introducing it to the main restaurant menu.
Branches matter because they allow you to experiment safely, fix bugs, or build new features without risking your stable project files.
- Creates safe experimental workspaces
- Prevents breaking main code
- Allows multiple ideas at once
- Uses the branch command
- Ask to merge your new branch changes back into your main project on GitHub.GitHub Docs
Read more
Asking to merge your new branch changes back into your main project on GitHub is the standard way to review work. It invites feedback before updating.
Think of it as showing your draft essay to a teacher or friend, asking them to read it and approve changes before you print the final copy.
This is essential for collaboration, ensuring every change is reviewed and tested before becoming part of the main project.
- Requests code review online
- Merges experimental branches
- Invites team feedback
- Finalises project updates