A city parking-meter integration engineer experiments with a local Git commit that was never pushed. Overnight they realize the experiment should not stay in history. Separately, a shared branch already has a bad commit that three other civic apps have pulled. Which actions match those two situations?
Select an answer to reveal the explanation.
Short Explanation
Think of reset as quietly rewriting a diary nobody else has read, and revert as posting a public correction notice. Local-only experiments can be reset; shared history needs a new revert commit so collaborators stay in sync.
Full Explanation
DEVCOR task 1.10 distinguishes reset (rewrite local history that has not been published) from revert (add a compensating commit when others already based work on the bad change). Applying reset to a published commit forces painful force-pushes and broken clones across the municipal team. Cherry-pick and stash are not the judgment this scenario asks for.