Skip to content
Module
Module 3 of 6Lesson 1 of 2~20 min

Everyday commands, and what can go wrong

Most Git incidents come from a command run without knowing exactly what it changes. This lesson walks you through a day of contributing, on the command line or in GitHub, so you understand the effect of each step and catch a mistake before it reaches the shared repository.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to chain the Git commands of a contribution day (clone, switch -c, status, diff, add -p, commit, push -u, fetch, pull, log) or their GitHub equivalents, knowing what each one changes and how to spot a mistake before it reaches the shared repository.

Topics covered

  • Git commands
  • Git command line
  • GitHub without a terminal
  • commit and push
  • Git mistakes

Where it fits

Work on a branch, day to day

Which commands do I use, in what order, and how do I name my work?

Lessons in this module

  1. Everyday commands, and what can go wrong (this lesson)
  2. Branching strategy and commit messages

What you will learn in this module

This lesson is part of the course Git for PMs: ship as a team without putting production at risk

  • Work on a short-lived branch with everyday Git commands (or their GitHub equivalents), small commits named by convention, and stay in sync with main.

Related courses