Bug fix · mastra-ai/mastra
Keep Factory merge handling scoped to built-in boards
The default Factory GitHub rule now returns no decision for merged pull requests on custom boards. This leaves lifecycle decisions to custom rules while preserving built-in Review and Work behavior.
The problem
When a pull request associated with a custom Factory board merged, the default GitHub rule emitted a transition targeting the built-in Work board. Ingress rejected the cross-board transition, leaving the custom-board card without a merge decision.
The approach
Added an early return for non-Work boards after the existing Review-board handling. Added a regression test using a merged pull request on a `release` board and asserting an undefined decision. Included a patch changeset for `@mastra/factory`; the PR reports all 75 focused rule tests and `git diff --check` passing.
What changed
Custom-board merge events no longer produce invalid Work-board transitions from the default rule. Existing Review and Work merge handling remains in place.
- typescript
- github
- factory
- event-handling
- regression-testing