CB-576: release preserves a dirty worktree instead of deleting it #53
Reference in New Issue
Block a user
Delete Branch "worker/cb576-01a04b-17"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Releasing a COMPLETED session whose worktree holds uncommitted work now preserves the directory and logs a WARN instead of --force-deleting the worker's only copy of its work (the exact shape lost in the incident: a worker that ended a turn without committing).
Tests: mvn -f bridged/pom.xml clean install -> BUILD SUCCESS, Tests run: 678, Failures: 0, Errors: 0, Skipped: 0
0b081deb5eto9118ce2537