In version control, what does a commit represent?

In version control, what does a commit represent?

• A. A commit is a complete copy of the repository.
• B. A commit saves a snapshot of changes in the repository.
• C. A commit only records code formatting.
• D. A commit merges two branches.

Answer: (B)

In version control, a commit represents a snapshot of changes saved to the repository at a specific point in time. It records what changed since the previous commit, stores those changes (typically efficiently by recording only the deltas), and includes metadata like who made the change, when, and a message describing it. This creates a historical trail you can review, revert to, or use to build branches. A commit isn’t a full copy of the entire repository each time, and it isn’t inherently about merging branches—that’s a separate operation that may create a merge commit.

In version control, a commit represents a snapshot of changes saved to the repository at a specific point in time. It records what changed since the previous commit, stores those changes (typically efficiently by recording only the deltas), and includes metadata like who made the change, when, and a message describing it. This creates a historical trail you can review, revert to, or use to build branches. A commit isn’t a full copy of the entire repository each time, and it isn’t inherently about merging branches—that’s a separate operation that may create a merge commit.