feat(FN-670): add mandatory build verification before merge
- Add report_build_failure tool to merger agent for explicit build failure signaling - Run buildCommand before finalizing merge, abort if build fails with git reset --merge - Treat build failures as fatal errors (no retry) and keep task in in-review - Add build verification instruction to executor system prompt - Update executor to use steeringComments field for mid-execution guidance
This commit is contained in:
14
.changeset/build-verification-before-merge.md
Normal file
14
.changeset/build-verification-before-merge.md
Normal file
@@ -0,0 +1,14 @@
|
||||
---
|
||||
"@gsxdsm/fusion": patch
|
||||
---
|
||||
|
||||
Add mandatory build verification before merging to main
|
||||
|
||||
The merger agent now verifies that the build passes before committing a squash merge:
|
||||
|
||||
- When `buildCommand` is configured in settings, the merger runs it before finalizing the merge
|
||||
- If the build fails, the merge is aborted with `git reset --merge`, the failure is logged, and the task remains in "in-review" for human investigation
|
||||
- A new `report_build_failure` tool allows the agent to signal build failures explicitly
|
||||
- The executor prompt now reminds agents to verify the build passes before calling `task_done()`
|
||||
|
||||
This ensures broken code never reaches the main branch.
|
||||
Reference in New Issue
Block a user