Git Patch Workflows Quiz

Check your understanding of mailbox patch generation, raw diff application, and the boundaries between format-patch, apply, and am.

8 questions

Knowledge check

Check your understanding of mailbox patch generation, raw diff application, and the boundaries between format-patch, apply, and am.

You can retake this quiz whenever you like.

0:00

0/0

What does `git format-patch BASE..HEAD` normally create?

It formats selected commits as separate mailbox-style patch messages.
What does `git apply` do by default?

Without `--cached` or `--index`, `git apply` applies the patch to files in the working tree and does not create a commit.
Why use `git apply --check change.patch`?

`--check` performs the applicability check without applying the patch.
Which option applies a patch only to the index?

`--cached` applies the patch only to the index.
Which command is the intended next surface for turning `git format-patch` mailbox messages back into commits?

`git am` applies mailbox-formatted patches and creates commits from them.
What does `git apply -R change.patch` do?

`--reverse` applies the patch in the opposite direction.
What is the purpose of `--cover-letter` in `git format-patch`?

It generates a cover-letter file alongside the patch series.
Which statement is correct?

`git diff` can generate unified diff text; `git apply` consumes that text, while format-patch creates mailbox-style messages for workflows such as git am.

What does `git format-patch BASE..HEAD` normally create?