Name the snapshot.
Then share it as a pull request.

Why version control exists

Version control exists so a team can name a snapshot, see who changed it, and return to it without keeping extra copies of the whole file.

Repositories and the three states

Create your first persisted repository here. git status reads those three states. The graph starts with the initial commit.

After Why version control exists

Commits

write a file, git add it, and git commit. Each commit appears on the graph of this repository.

After Repositories and the three states

Branches

Create a branch, commit on it, and switch back. Watch the label and HEAD move.

After Commits

Merging

Merge a branch that diverged. The graph shows either a moved label or a commit with two parent hashes.

After Branches

Rebase compared with merge

Use the side-by-side player. The same start becomes two different graphs.

After Merging

Undoing changes

Stash a dirty tree, then compare reset and revert on a commit you have not pushed.

After Rebase compared with merge

Remotes and collaboration

Add origin, push a branch, and clone a visible repository on this platform.

After Undoing changes

Issues and pull requests

Open an issue and a pull request on your repository. They stay in this platform's tables.

After Remotes and collaboration

Code review

Leave a review comment on your pull request and read it back as part of the request, not as a chat log.

After Issues and pull requests

Merge conflicts

Load the conflict exercise, edit the file until the markers are gone, then add and commit.

After Code review

Branch conventions and commit messages

Name a branch and a commit so a teammate can tell the intent without opening the diff.

After Merge conflicts

Feature ownership and branch-based work

Fork the teacher's shared starter repo, then commit on a branch that the starter does not have.

After Branch conventions and commit messages

Opening a cross-repo pull request

Open a pull request from your branch toward the class's shared starter repository.

After Feature ownership and branch-based work

Giving and receiving review

Leave a peer comment on a pull request aimed at the shared starter, then answer review with a commit.

After Opening a cross-repo pull request

Resolving conflicts with a teammate

Fetch the shared starter after a classmate's merge, catch up your branch, and resolve any conflict with that teacher-approved history.

After Giving and receiving review

Handover and documentation

Commit a README note that says what the branch is for and what to read next.

After Resolving conflicts with a teammate