Unverified50% confidenceFactExact time
Squash 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedDirectly 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.76% similarUnverifiedPatches must be idempotent and replayable, and must preserve the original file's line endings; otherwise, a two-line fix can propagate into changes across the entire file.65% similarUnverifiedTraditional Postgres PITR relies on a base full backup plus WAL archiving, requiring restoration of the full backup followed by serial replay of all WAL logs during recovery.62% similarUnverifiedCredential replay refers to a credential being used again outside the context in which it was issued; it requires no breaking of cryptographic algorithms, only copying a key that is still within its validity period.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1043636API
curl https://kongchang.com/api/v1/knowledge/claims/1043636MCP
get_claim(id=1043636)