GitLab Approval Tracker

Track your GitLab merge requests and pending reviews. Real-time notifications for new approvals.

Never miss a merge request approval again. GitLab Approval Tracker monitors your GitLab merge requests across all projects and notifies you the moment someone approves — or when a new MR lands on your review queue. FEATURES • Two-way tracking — see MRs you created (waiting for approvals) and MRs where you're a reviewer (waiting for your action) • Real-time notifications — desktop alerts with optional sound when approvals arrive or new review requests appear • Multi-project support — works across all GitLab projects accessible with your token, no configuration per project needed • Smart polling — only checks approvals for MRs that actually changed, minimizing API calls • Encrypted token storage — your GitLab access token is encrypted with AES-256-GCM using a password you set; decrypted token lives only in session memory and is cleared when the browser closes • Bilingual UI — English and Russian, or auto-detect from system language • Collapsible sections — tracked MRs and pending reviews collapse independently to keep the popup compact • Badge counter — shows total number of tracked and pending MRs at a glance HOW IT WORKS 1. Create a GitLab Personal Access Token with the read_api scope 2. Install the extension, set a password and paste the token 3. The extension polls GitLab on the interval you choose (15–120 min) 4. You get notified about new approvals, new MRs, merged MRs, and new review requests PERMISSIONS EXPLAINED • notifications — desktop alerts for approvals and review requests • alarms — periodic background checks on the interval you set • storage — encrypted token and settings persistence • tabs — open the MR in a new tab when you click a notification • offscreen — play notification sound (service workers cannot play audio directly) • host_permissions (your GitLab host) — API requests to fetch merge request data PRIVACY • Your GitLab token is encrypted at rest with AES-256-GCM (PBKDF2-derived key) • The decrypted token exists only in session memory — cleared on browser close • No data is sent anywhere except your GitLab instance • No analytics, no tracking, no third-party services • Strict Content Security Policy blocks all external connections