Automatic self-maintenance needs the GitHub integration. The background flow reads your repo to detect changes on the default branch, so without the GitHub integration active and pointed at the right repo, Mini has nothing to watch.
What it covers
Microscopic drift
A renamed button, a tweaked label, a reordered form. The story stays; criteria are rewritten to match what’s on screen now.
Macroscopic drift
A whole feature removed, a new journey shipped. Stories are added or retired.
Connective tissue
Dependencies between stories get wired automatically. Existing profiles get linked to the journeys that need them.
How it works
Mini watches what lands on the default branch (main in most cases). When the diff is meaningful, it opens a draft with the updates: new stories, retired ones, and criteria rewritten to match the new UI.
Mini then builds the merge commit and checks the changed stories on a device. Your suite keeps running the current stories until the draft merges.
You don’t trigger it, and you don’t review every change. On the Drafts page, Mini’s drafts that need nobody sit folded under Mini’s maintenance, merge on their own once proven, and then move to History. Only the ones that need you, to answer a question or to merge, show at the top of the list.
What stays manual
Two things Mini can’t infer from code alone:New profiles
If a new journey needs a new identity (a
Pro user to test a paywall, an Admin for a settings screen), you’ll be prompted to provide the credentials. Existing profiles get linked automatically.Device files
Photos to upload, PDFs to attach, audio to play back. Anything that lives outside your repo, you attach by hand.