A clean Git history is often maintained by using _______ to combine commits before merging.
- git squash
- git merge --squash
- git combine
- git rebase -i
The correct option is git rebase -i. Interactive rebase (-i) allows you to combine, edit, or reorder commits interactively. Squashing commits during interactive rebase helps create a cleaner and more organized Git history before merging into the main branch.
Loading...
Related Quiz
- In a complex project workflow, a __________ Git hook can enforce commit message standards.
- How does GitHub Actions integrate with Git workflows for CI/CD?
- In what scenario is rebasing preferred over merging in Git?
- A team is handling an urgent bug fix in a production application. Which branch in the Gitflow model should they use?
- What advanced Git feature can be crucial for performance optimization in large-scale enterprise projects?