Software Engineering · Question 25 · Medium
Software Engineering question 25
A bad commit has already been pushed to a shared main branch that teammates have pulled. Which command safely undoes its effect without rewriting history?
- git revert <commit>
- git reset --hard <commit>~1 followed by git push --force
- git commit --amend
- git checkout <commit>
Answer and explanation
Answer: A. git revert <commit>
Explanation: git revert creates a new commit that applies the inverse changes, so the existing history stays intact for everyone. Resetting and force-pushing rewrites shared history and disrupts teammates.
Previous: You have uncommitted changes but must switch branches quickly to fix an urgent… · Next: A Scrum team completed 30, 34 and 26 story points in its last three sprints…
Practise software engineering
Try a fresh set of software engineering questions with an explanation after every answer, free and without signing up: Software Engineering practice. Or sit a full placement mock test.
More software engineering questions
- What is the minimum number of test cases needed for 100% branch (decision)…
- Which type of coupling between modules is considered the worst (strongest)?
- You have uncommitted changes but must switch branches quickly to fix an urgent…
- A Scrum team completed 30, 34 and 26 story points in its last three sprints…
- What is the cyclomatic complexity of this procedure?
- Using Basic COCOMO in organic mode, Effort = 2.4 × (KLOC)^1.05 person-months…
- In mutation testing, 50 mutants are generated. 5 of them are equivalent…
- Why should you avoid rebasing commits that have already been pushed to a…
More technical & programming practice
Cloud & DevOps · GenAI Basics · Pseudo-code · C Programming · Java · Python · Data Structures · Algorithms
LogicWiz Exams home · All practice topics · Placement mock tests · Daily 10 challenge