workspace.export: add base_commit to capture worker git commits
Without base_commit, export diffs against the current guest HEAD. If the worker ran git commit inside the VM, HEAD advanced and the diff came back empty — committed work was silently lost. With base_commit set to the head_commit from workspace.prepare, the diff uses that fixed point instead. After git add -A the index holds the full working state, so git diff --cached <base_commit> captures everything: committed deltas (HEAD moved past base) and any uncommitted changes on top, in one patch, applied with the same git apply flow. - WorkspaceExportParams gains base_commit - WorkspaceExportResult echoes back the ref actually used - CLI gains --base-commit flag - Tests assert scripts use the caller-supplied ref and that omitting it falls back to HEAD
This commit is contained in:
parent
94c353f317
commit
ff51b7ce21
6 changed files with 162 additions and 10 deletions
|
|
@ -1,5 +1,7 @@
|
|||
# Repository Guidelines
|
||||
|
||||
Always run `make build` before commit.
|
||||
|
||||
## Project Structure
|
||||
|
||||
- `cmd/banger` and `cmd/bangerd` are the main user entrypoints.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue