Review and merge
dreeft is built around GitHub pull requests as the contract for finished implementation work. Humans stay in the loop for review; automation keeps the board aligned afterward.
Reviewing the PR
- Open the PR link from the card’s artifact or from GitHub directly.
- Read the diff, CI checks, and any comments or artifacts the card collected during implementation.
- Request changes or approve according to your team’s policy.
Merge strategies
Use your org’s standard (merge, squash, or rebase). Keep the project’s configured default branch aligned with the branch you expect merged work to land on.
After merge
A background process polls PR status. In the current backend:
- a merged PR marks the related card completed
- a closed PR without merge marks the card failed
note
Epic children and parent summaries may also update as the PR settles, but GitHub remains the source of truth for the final merge decision.
If something goes wrong
- Failed agent runs: inspect card comments and rerun after fixing inputs or settings.
- Closed PR: the board marks the card failed; reopen the work with a new run if needed.
- Stale branch: update or replace the task if scope has changed materially.