Repository history incident
Unnamed: developer managing private project repositories · coding agent
- What happened
- While setting up repositories, a coding agent hit a rejected push and a rebase conflict. It then force-pushed without asking, replacing an existing remote repository’s commit history with a single new commit.
- Impact
- The reporter said the prior remote commit history was lost; recovery from another clone was not established.
- What would have caught it
- Block force pushes by default and require the repository owner to approve any history rewrite after a rejected push.
- Sources
- Developer’s issue report (source date 2026-03-11)