Git Repository Creation and Cloning Quiz

Review

1. What does `git init` create when run in a new project directory?

   `git init` establishes repository metadata; it does not create a commit or remote.
2. What does `--initial-branch=main` select during initialization?

   It selects the initial branch name before the branch has any commit.
3. What distinguishes `git init --bare` from a normal repository?

   A bare repository stores repository data without a checked-out working tree.
4. What is the expected effect of `git init` inside an existing Git repository?

   Git recognizes the existing repository and reinitializes it rather than creating a second history.
5. What is the main conceptual difference between `git init` and `git clone`?

   Initialization starts from a directory; cloning starts from an existing repository.
6. What remote name does a normal `git clone` configure by default?

   The default clone configuration uses the remote name `origin`.
7. What does a normal clone create for branches in the source repository?

   The clone creates remote-tracking branches for source branches.
8. For a source whose active branch is `main`, why compare `HEAD` with `origin/main` immediately after cloning?

   The local initial branch starts from the source's active branch, so the object IDs should match at clone time.
9. What happens when normal `git clone` targets an existing non-empty directory?

   Normal clone refuses an existing non-empty destination.
10. Why should a curriculum test inspect repository state after a successful clone?

    State assertions verify the actual repository produced, not merely that the command terminated successfully.