Your browser is blocking local storage, so your progress will be lost when you close or reload this page.

Track, share and review changes safely with Git.

Topics

• Git FundamentalsExpected level: Proficient

  Clone, commit, push, pull, fetch, and sync code safely.

  Not reviewed
• Branching and MergingExpected level: Proficient

  Work independently while collaborating with other developers.

  Not reviewed
• Resolving Merge ConflictsExpected level: Working

  Understand how conflicts occur and how to resolve them correctly.

  Not reviewed
• Commit HygieneExpected level: Proficient

  Write small, meaningful commits that tell the story of a change.

  Not reviewed
• Ignoring and Excluding FilesExpected level: Working

  Keep generated files, secrets, and local settings out of the repository.

  Not reviewed
• Pull Requests and Code ReviewsExpected level: Proficient

  Participate in collaborative development and quality control.

  Not reviewed
• SSH Keys and Git AuthenticationExpected level: Working

  Use key pairs or tokens to authenticate to Git remotes and other systems.

  Not reviewed
• Repository StructureExpected level: Working

  Understand common layouts, documentation, and project organization.

  Not reviewed
• Undoing MistakesExpected level: Working

  Safely discard, revert, amend, and recover work.

  Not reviewed

Self-assessment

You should be able to do each of these without help.

• Authenticate to a Git remote using an SSH key or token. You should be able to set it up on a new machine and fix it when a push is rejected for authentication reasons.Related: SSH Keys and Git Authentication
• Clone a repository, create a branch, commit, push, and open a pull request. Do the whole sequence once from start to finish, using only the command line and the hosting website.Related: Git Fundamentals, Branching and Merging, Pull Requests and Code Reviews
• Update your feature branch with the latest changes from main. Say whether you merged or rebased, and why you never rebase commits that others have already pulled.Related: Branching and Merging
• Resolve a simple merge conflict. Read the conflict markers, choose the correct result, and finish the merge with a working build.Related: Resolving Merge Conflicts
• Write a commit message that explains why a change was made. A colleague reading the log in six months should understand the reason without opening the diff.Related: Commit Hygiene
• Keep generated files out of a repository with a .gitignore file. Cover build output and local settings, and stop tracking a file that was already committed.Related: Ignoring and Excluding Files
• Respond correctly when a password or key has been committed. Revoke or rotate it first, then remove it from the code, and tell the people who need to know.Related: Secrets Management, Ignoring and Excluding Files
• Undo a change without losing other work. Choose between discarding a file, amending a local commit and reverting a pushed one, and know which of them rewrite history.Related: Undoing Mistakes
• Review a colleague's pull request and leave useful comments. Point to specific lines, explain the concern, and say what you would suggest instead.Related: Pull Requests and Code Reviews, Giving and Receiving Feedback
• Open a pull request that a reviewer can approve quickly. Keep it small, explain what changed, why and how to test it, and answer every review comment by fixing it or giving a reason.Related: Pull Requests and Code Reviews, Giving and Receiving Feedback