Mergerie
Contents

Settings

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

Repository groups

Twenty micro-services of one team share the same review rules, the same verification commands, the same template. A configuration file in every repository would duplicate them twenty times; a group carries them once. Settings → Repositories → Repository groups: a name, its members (ticked behind a filter that hides without unticking) and, folded, its templates (review, fix, modification) and standing instructions — empty, the global settings apply. Resolution is global → group(s) → repository: a repository can be in several groups, the oldest one carrying a value wins, and the repository's sheet says where each value comes from.

What a group also carries: a review rule can be limited to it (it applies to every member, present and future), and a verifier can cover it as a whole (in worktree mode — “in place” and its consent stay line by line, a machine's folder is not declared for twenty repositories). Wherever repositories are picked — a multi-repository session, a Git action, a verifier's coverage — one chip per group adds or ticks all its members.

The group belongs to the team: it travels through the data repository, its members designated by their address (forge/project), and a repository a machine does not track is kept aside, never lost. What executes keeps the verifiers' rule: a group coverage that arrives through the sync waits for approval on each machine; a template or a rule travels freely, its text entering the prompt tagged as data.

Every field carries a “team” or “this machine” badge, because settings are not all of the same kind. A team setting describes the tool: the prompt templates, the thresholds, the review policies, the forge address — two reviews of the same merge request written under different instructions are not comparable, so those settings are meant to be shared. A this machine setting belongs to your computer alone: the API tokens, the clone folder, the language. They are stored apart, in a table that is never meant to travel: that is what will later let a team share its tool without a single secret leaving anyone's machine. A copy button sits next to every token field (GitLab, GitHub, Jira, Confluence, a plugin's own secret…): the field itself still only ever shows ***, the button asks the server for the value on that click and writes it straight to the clipboard.

Sub-tabs, in the order of the journey — connect, choose the code, tune the review, tune the tool, the optional integrations, the test bench. Every save, on any sub-tab, now confirms with a toast once it lands (an error toast if the server refuses):

Git (the GitLab connection — URL + access token, with Test the connection —, the GitHub connection — URL (empty = github.com, otherwise GitHub Enterprise)

  • token, with Test GitHub —, the clone folder, and the git command palette of the Git → Git commands tab: add/edit/delete commands as name + fixed command). It comes first, and it is the one that opens on a fresh install: without a token no other setting is worth anything · Repositories (added one by one or in bulk from GitLab or from GitHub — a pasted address is assigned to its forge by its host, compared with the hosts configured above first, so a GitHub Enterprise on a name without “github” in it lands on the right side; each repository carries a forge badge, and the same path can exist on both; without a token for that forge, the bulk-add window says so and points to the field to fill —, plus the local directories — a folder on your machine holding one subfolder per git project, which feeds the Git → Navigate tab and Out-of-repo coding; the displayed count “n git projects out of m folders” confirms at a glance that you pointed at the right level of the tree, and a button re-reads the directory from disk — a folder deleted by hand disappears, a repository cloned since appears, wherever the directory is offered; each repository also shows its open merge requests, the date of the last discovery and the state of its clone, with a Re-clone button — nothing is lost on the forge, but unpushed changes in the local clone are, so it asks first); a Sheet button unfolds what is attached to that repository — verifiers, Jenkins jobs, review rules limited to it, grid services, default linked projects, agents it belongs to. The row said what concerns IT; the sheet answers “what breaks if I remove it?” and “which verifier tests it, again?”. Every entry leads to the screen where the object is edited, and nothing is asked of the server until the panel is unfolded) · Merge Request (automatic refresh, convergence, how many days of silence mark a merge request as dormant, and under Discovery the three overlap settings — Fetch the files of open MRs (checked; unchecked, no extra forge call and no badge), At most N file lists fetched per discovery (20; 0 = no limit) and Also overlap MRs with different target branches (unchecked), then Fetch the commits of open MRs (checked; it shares the files cap, an MR fetched for its files is fetched for its commits in the same round; unchecked, no extra call and no contains !214 badge) —, then those of the tests touched — Show the tests touched (checked; it depends on the file fetch, and says so), Flag the absence of tests from N code files (3; 0 = always), and the two pattern lists, test and neutral, one glob per line, with Reset to defaults and a preview "on the open MRs, these patterns classify 41 files as tests, 12 as neutral"; an invalid glob is refused on save with its line, a list of more than 100 lines too. The same two lists can be set on a repository (its unfolded row in Repositories) and on a group (its form): filled, they replace the level above; empty, the level above applies; then those of the dependencies — Show the dependencies (checked; unchecked, no manifest diff is kept and no badge shows) and the manifest patterns, one glob per line, with Reset to defaults and the preview "on the open MRs, these patterns designate 3 manifests", also settable on a repository and on a group, next to the test patterns —, then the registry check — Check added dependencies against the public registries (unchecked by default: it is Mergerie's first network call that goes neither to the forge nor to Jira, and the label names the hosts: registry.npmjs.org, repo.packagist.org, pypi.org, crates.io, rubygems.org, proxy.golang.org, search.maven.org, api.nuget.org — only for the packages your merge requests add, and only their name), Recent: published less than N days ago (30), At most N calls per round (30; 0 = no limit, independent of the file cap), the private package patterns (one name glob per line, empty; also on a repository and on a group, same resolution as the manifest patterns) and, this workstation's and never shared, the URL per registry (one ecosystem=url line per registry to override — a mirror, a company proxy; empty after the =, the ecosystem is not checked) —, prompt templates — the shipped template invokes no skill; write yours into it if you have one. Left empty, the review prompt asks for a structured report: findings ranked 🔴 blocking / 🟠 important / 🟡 minor, an overall score calibrated on named anchors — a score of 7 or more excludes any remaining blocker —, a “what's good” section and a merge checklist; a prompt you customised is untouched, and an installation still on the previous default picks the new one up by itself, in its language. The overall score, though, is asked for by the application whatever the template, because the list filters on it) · Specific review rules (a rule can be limited to one repository — without which you had to guess a path_match only that repository would satisfy; criteria added to the prompt when the branch name contains a given fragment or when the diff touches a path — a glob such as **/migrations/**, *.sql, which is more precise; a rule on a path can carry a “risk” badge shown on the merge requests concerned, computed without AI just from the diff's paths, to see at a glance which one to review first) · Verifiers (your test commands, and the repositories each of them can test — see Objective verification below; the page shows the list first, and the form opens on Add a verifier, Edit or Duplicate — the latter reopens it prefilled with no id, so saving creates instead of overwriting the original, with a free name proposed ("X (copy)", since names are unique) and the field selected: renaming is the first gesture; the form suggests the commands the covered repositories already declare — package.json scripts (with npm, pnpm or yarn after the lockfile), composer.json scripts and phpunit, Makefile targets, pytest / tox / ruff, go build|vet|test ./..., cargo build|test|clippy, mvn/./mvnw -B test, gradle/./gradlew test, dotnet test, read from the clone on disk, nothing is executed — to add in one click; when a compose file is in the clone, the docker compose run --rm <service> <command> variant of every test command is offered too: the commands run on the host, and it is in the line that you say to enter a container; every suggestion is an exact line, the one that will be approved as is) · General (with its own Save button — the fields of every sub-tab belong to the same form, and this one had none: you ticked a box and nothing left; light/dark/auto theme, language, density, menu arrangement, morning brief, data retention, backup, and a danger zone for a full reset) · Notifications (a dedicated sub-tab, see below) · Shared data (the git repository a team uses to share its accumulated settings, templates and rules — see Sharing with a team below) · Jira (the Jira connection — URL + email + API token, with a Test Jira button —, and “Tell Jira when the merge request is created” — ticked by default in a new session's window — with an editable comment template ({url}, {iid}, {project}, {title}, {branch}, {target}, {key}, a live preview; empty keeps the shipped message, shared with the team like the review-link template) —, and “Tell Jira when a merge request is merged”, unticked by default, with its own template — same variables, same preview: when Mergerie sees the merge request merged (discovery, Refresh from the forge), the ticket gets one comment — a single one per ticket, rewritten with the full list at each following merge request —, nothing for a close without merge nor from a period catch-up —; feeds the Jira tab and the enrichment of a session from a ticket) · Plugins (every installed plugin, its version, state and permissions; enable or disable it without restarting; install a third-party plugin from a local folder or a git address — this is where Jenkins, Docker and Links are installed and updated. An enabled plugin that declares its own settings adds its own sub-tab here, right after this one — Jenkins, for instance, brings back its URL, user, API token, jobs' refresh interval, linked jobs and “Announce ALL jobs” setting exactly where they used to live) · AI sessions (the agent binaries — the default and the others, see Configuration —, the standing instructions, see below, the daily limits, secure or yolo mode, the three boxes ticked by default on a new session — auto-push, the AI may ask questions, converge afterwards — moved here from General, and a technical test: two passes inside the same agent session — it memorises a marker then recalls it on resume — to check that session resuming works with your CLI; it is the foundation of context continuity between review, fixes and convergence. One Save bar, pinned to the bottom of the screen, now covers every section above instead of five identical buttons — it says unsaved changes as soon as a field changes, then saved).

The first three are what you fill in to get started; Rules and Verifiers complete the review; the rest is tuned when the need arises. The last sub-tab you visited is remembered — you come back to Settings to finish what you were doing there.

Standing instructions

Settings → AI sessions. Free text appended to the prompt of every coding session — in a repository and out of one, on the first run as on every follow-up. It is what you repeat every time: the language of comments, a command to run before committing, something not to do. Copying it into every prompt works until the day you forget — and that is always the one you re-read three hours later.

It comes after the task (what to do first, how to do it next) and before the questions block, which stays the last word. It is re-read on every prompt: an instruction added now applies to the session started right after, without restarting the tool. An empty field adds nothing — not even an orphan section heading. ⚠ It does not apply to exploration, which produces no code.