Git mktag Quiz

Review

1. What does `git mktag` create?

   `git mktag` constructs and writes a tag object from tag contents read on standard input.
2. Which command layer owns the creation of the `refs/tags/...` reference in a normal annotated-tag workflow?

   `git mktag` writes the tag object; ordinary tag-reference management belongs to the tag porcelain/ref commands.
3. Which header identifies the object targeted by a tag object?

   The canonical tag-object contents use the `object` header for the referenced object ID.
4. Why does changing the annotation message change the resulting tag-object ID?

   A Git object ID is derived from the object's type and complete content, so changing the message changes the object ID.
5. What is a key difference between `git mktag` and `git hash-object -t tag -w`?

   The official documentation describes `mktag` as the validating construction path for tag objects.
6. How can you inspect the type of the object ID printed by `git mktag`?

   `git cat-file -t` reports the Git object type.
7. What should happen when a validly structured tag input names a nonexistent target object?

   `mktag` validates the referenced object and rejects an invalid target in the tested Git version.
8. What does `--no-strict` do for `git mktag`?

   The current official documentation says `mktag` enables the equivalent of `git fsck --strict` by default and provides `--no-strict` to disable it.
9. Which existing Foxipa lesson remains the owner of normal lightweight and annotated tag workflows?

   `git mktag` is a plumbing/object-construction lesson; normal tag-reference workflows remain in the dedicated tags lesson.