Review Rail
Overview
Personal code review queue for GitLab, self-hosted or gitlab.com. Know what to review next. All data stays in your browser.
Review Rail turns your GitLab merge requests into a personal, ordered review queue. It answers "what do I review next" — not just "what is open". Works with gitlab.com and any self-hosted GitLab. Private by design: a read-only token (scope: read_api), no backend, no analytics — your merge requests stay between your browser and your GitLab. QUEUE • Merge requests where you are a reviewer are picked up automatically • "Up next" always shows the one MR to open now • MRs with your urgency label (e.g. "asap") jump to the top • Drag cards to reprioritize; hide MRs you don't need to review STATUS TRACKING • After you request changes or comment, the MR moves to a waiting section • When the author re-requests review, it returns to the queue automatically STATS • Reviews today / this week / this month / all time • Contribution-style activity grid for the last 16 weeks • History is backfilled from GitLab with real dates HONEST NUMBERS • A review is counted only on real GitLab actions: an approval, a submitted review, or a merged or closed MR with your comments Requires GitLab 13.8+; reviewer-state features need GitLab 16.9+. Review Rail is under active development (0.x). Found a rough edge? Report it on GitHub.
0 out of 5No ratings
Details
- Version0.2.2
- UpdatedAugust 6, 2026
- Offered byEvan Vesmirov
- Size50.87KiB
- LanguagesEnglish (United States)
- Developer
Email
dev@vesmirov.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site