Unverified50% confidenceFactExact time
A revert merely adds a commit with a reverse patch; the original commit still exists in the history graph and is still reachable from B; reachable does not equal in effect, nor does it equal released.
1
Sources
50%
Confidence
Long-term
Relevance
10/17/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe same version history also records the process of retractions, proof fixes, and clarifications of assumptions.64% similarUnverifiedDirectly reverting a merge commit makes git think those commits have already been merged, so when a subsequent agent fix branch is merged again, only the new fix comes in, while the rest of the work remains in the reverted state.63% similarUnverifiedApproval requests now preserve the pre-transform input, avoiding the transform being executed twice when resuming execution.63% similarUnverifiedRetaining a complete change history allows humans to trace the source of modifications and restore earlier versions, the same logic as version control systems such as Git.62% similarUnverifiedSquash never records the agent's commits as merged, so squashing the fixed branch again brings back all the work; a reverted merge commit is different, and it requires first reverting that revert before it can land again.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1057035API
curl https://kongchang.com/api/v1/knowledge/claims/1057035MCP
get_claim(id=1057035)