Skip to content

Git and GitHub roadmap

Track every change, collaborate without fear, and automate the boring parts.

4 to 6 weeks at 5 to 6 hours a week6 stages33 topicsBeginner friendly

All roadmaps

Git records the history of your work and GitHub is where teams review and ship it. Every developer and DevOps role expects you to be fluent in both. This path moves from the mental model to team workflows, automation and repository security.

Where you will end up

You can work in any team repository: branch, commit cleanly, resolve conflicts, recover from mistakes, review pull requests and set up an automated workflow that tests and secures a project.

Before you start

  • A computer where you can install Git
  • A free GitHub account with two-factor authentication turned on

Roles it leads to

  • Any software developer role
  • DevOps Engineer
  • Technical Writer or Open Source Contributor
  1. 1

    Git fundamentals

    1 week0 of 5 done

    Understand what Git stores and use the everyday commands without guessing.

    Prove it

    A clean history

    Create a small project with at least ten commits that each do one thing, each with a clear message, plus a sensible .gitignore.

  2. 2

    Branching and history

    1 to 2 weeks0 of 6 done

    Work on changes in isolation, combine them, and fix mistakes safely.

    Prove it

    Break it and recover

    Create a conflict on purpose and resolve it. Then reset your repository badly and use the reflog to bring everything back.

  3. 3

    Remotes and collaboration

    1 to 2 weeks0 of 5 done

    Share work with other people through GitHub and contribute to someone else's project.

    Prove it

    A merged contribution

    Contribute a real improvement, such as a documentation fix, to an open source project and get it merged. Link the pull request in your portfolio.

  4. 4

    Team workflows

    1 week0 of 4 done

    Pick a branching strategy and enforce it so the main branch is always releasable.

    Prove it

    A protected main branch

    Configure a repository so nothing reaches main without a pull request, an approval and green checks. Demonstrate that a direct push is rejected.

  5. 5

    Automation with GitHub Actions

    1 to 2 weeks0 of 5 done

    Let GitHub test, build and deploy your project on every change.

    Prove it

    Test on every pull request

    Add a workflow that lints and tests your project, make it a required check on main, and add a deployment job that needs a manual approval.

  6. 6

    Repository security and hygiene

    1 week0 of 5 done

    Keep code and credentials safe and make your repositories easy for others to use.

    Prove it

    A repository you would be proud to show

    Enable alerts and updates, add scanning, and write a README that lets a stranger run the project in five minutes. Pin it on your GitHub profile.

Certifications that fit

Optional, and never a substitute for projects. Exam details change, so confirm on the official page before you book.

The honest part

You will learn Git properly the first time you make a serious mistake and recover from it, so practise in a throwaway repository where nothing matters. Keep your real work public if you can: contribution history on your profile is quiet, honest proof of consistent effort.

Checked against

Written by CloudIskole and reviewed against the official sources below. Last verified November 2026. Spotted something out of date? Tell us and we will fix it.

These roadmaps are our own work. For another community view of learning paths, see roadmap.sh, which inspired the idea of a visual guide.