Large commits are discouraged because they:

Question

BlackTom AI · Accepted Answer

When evaluating why large commits are discouraged, it's helpful to consider how code reviews and collaboration work in practice.
Option 1: 'Cause Git to crash' — In general, large commits do not inherently cause Git to crash. Git is designed to handle large histories, and crashes are rare and typically due to tooling or unusual edge cases rather than the size of a commit itself. So this option is a misunderstanding of Git's robustness.
Option 2: 'Reduce runtime performance' — The size of a commit in the repository does not directly affect the runtime performance of the codebase at runtime. Performance is more influenced by the changes themselves, algorithms, and dependencies, not by how many changes are grouped into a single commit. Therefore this claim is not about the commit process but about the code’s behavior, making it misleading in this context.
Option 3: 'Cannot be merged' — A large commit can be merged if it passes the review and tests, so claiming it cannot be merged is inaccurate. Mergeability depends on conflicts, test results, and policy, not strictly on the size of the commit. Thus this option is incorrect.
Option 4: 'Are harder to review effectively' — This aligns with common best practices: large commits tend to bundle many changes, making it difficult for reviewers to understand the intent, spot regressions, and provide precise feedback. Smaller, focused commits help track rationale, enable targeted reviews, and simplify bisecting if issues arise. This option correctly identifies a key drawback of large commits.
In summary, the first three options misinterpret the impact or mechanics of commits, whereas the fourth option accurately reflects practical review challenges associated with large commits.

CPSC-491-01 Software Engineering (Fall 2025) CPSC 491 Exam 2

Large commits are discouraged because they:

View Explanation

Log in for full answers

Similar Questions

A pull request is used for:

Merge conflicts occur when:

Why create feature branches?

When you hit ‘commit’ in RStudio, your code changes will be visible on Github.

Git is a centralized version control system.

[table] Which documentation helps track project changes? [/table]

Match Git workflow steps to their descriptions: 1: Fork 2: Clone 3: Commit 4: Pull Request

What is one of the main advantages of Git’s distributed nature?

More Practical Tools for Students Powered by AI Study Helper

Homework AI Solver

Stylized AI Paper Writer

Plagiarism Checker Assistant

Citation AI Academic Writing Tool

In-Class Translation Assistant

AI Note Generator

AI Quiz Answers

Past Exam Questions from University Test Bank

Smart Practice Assistant

Adaptive Practice

Making Your Study Simpler