root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-1632): merge fusion/fn-1632

Browse Source
This commit is contained in:
gsxdsm
2026-04-12 15:28:10 -07:00
parent 9b20a99bae
commit 59edac4ce2
5 changed files with 499 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
.changeset/block-merge-on-failing-tests.md Normal file
View File

@@ -0,0 +1,16 @@
---
"@gsxdsm/fusion": minor
---
Block merges when review-cycle tests fail
When `settings.testCommand` is not explicitly configured, Fusion now automatically infers a default test command from the project's package manager lock file:
- `pnpm-lock.yaml` → `pnpm test`
- `yarn.lock` → `yarn test`
- `bun.lock` / `bun.lockb` → `bun test`
- `package-lock.json` → `npm test`
This ensures that merges are blocked when tests fail, even without manual configuration of `testCommand`. Explicit `settings.testCommand` always takes precedence over inferred defaults.
Verification failures remain hard blockers — non-zero exit codes prevent task completion and keep tasks out of `done`.