Mergerie
Contents

Desktop notifications

This page is generated from docs/guide.en.md · Edit this page on GitLab

System notifications for the moments that call for an action or close a wait — not for atmosphere. On by default: the end of the review queue (the batch, not each MR), a review under a score threshold (“MR !142: 4.2/10”, adjustable threshold), a job failure (timeout, CLI, network), a coding session finished and the AI has asked a question (a session is waiting for your answers to resume). Also on: a Git operation finished (branch created, tag pushed — the most irreversible gesture in the tool, and it used to happen in silence), a working folder not restored after an in place verification (the worst state the tool can leave behind, until now visible only by opening the report) and an automatic cap reached (merge requests left aside: a silent cap reads as “everything was done”). Off by default because they are informative: a new MR discovered, an MR merged and a container that went down — on a development machine, containers stop every day for good reasons.

What the server now watches on its own. The end of a Jenkins build you started from Mergerie was watched by the browser: it only arrived if the Jenkins tab had stayed open — when you start a build precisely to go and do something else. A background watch handles it server-side now, once a minute, and asks Jenkins nothing while no launch is pending. The same watch picks up fallen containers — a transition, never a state: a container stopped three days ago does not raise the alarm every morning. The notifications are persistent: they stay on screen until you click or dismiss them, so you do not miss them. A click on the notification brings you back to the right place (tab focus + opening the MR or the session concerned). A “silent mode” toggle in the bottom bar cuts everything in one click. Fine-grained settings live in the Settings → Notifications sub-tab, with the browser permission status (granted / denied / to be asked) and a Test button — because a permission silently denied is the classic trap of this API.