Question 130
During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A network automation feature branch contains many intermediate repair commits that obscure the single approved change being deployed. What should the engineer change first to resolve this specific issue?
Explanation
Correct Answer
Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. This addresses the problem because a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Confirm success using: The protected target branch contains one reviewed release commit whose diff matches the approved feature changes. Applied here, the relevant facts are: A network automation feature branch contains many intermediate repair commits that obscure the single approved change being deployed. The question asks what should the engineer change first to resolve this specific issue.
Incorrect Answers
This alternative is a response to another technical cause: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The reported case instead depends on: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The action that directly addresses it is “Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content”.
The proposed action belongs to the mechanism: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. Here the stated fault follows a different mechanism: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The corrective choice is “Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content”.
The offered action targets: unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. The case facts point instead to: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Implement “Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content” to address that specific condition.