Windows: a GitHub panel, with news of broken builds, checks, review requests and merged pull requests

[Edurique]

What

Turns the Windows GitHub pill into something you can read your GitHub from, without leaving for the browser: a richer card in the overview, a full panel behind it, and Mochi speaking up when a build of yours breaks, the checks of a pull request of yours end, somebody asks for your review, a pull request of yours is merged, or somebody opens a pull request on one of your projects. Read-only from end to end.

It is a big diff (about 10 000 lines, almost all in new files) and I know that is a lot to ask of a review. It is one topic, and I could not find a split that would show as separate diffs from a fork — but if you would rather have it in pieces (panel first, then news, then comments), say so and I will cut it.

Windows only. Nothing under NotchBuddy/ is touched. The aim is to port it to Swift afterwards if you like where it goes.

What it looks like

The card — the year's contributions, the last seven days, the latest activity.

The panel, on Activity: the contribution graph and the latest events. Clicking a day shows what was done that day, and Mochi takes that day's colour.

Projects, and a project's sheet.

A pull request, and its checks while they run — one mini Mochi per job, followed live.

A run, job by job.

Comments on a pull request, and a thread shown on the line of the diff it is about.

News: a merged pull request, a broken build — and, added since this was opened, a pull request somebody else opens on one of your projects (same card, saying who opened it; no screenshot of it yet). Each project of the Projects tab has a bell: a click mutes its news, another gives it back. Open goes to it; OK folds the island and leaves the news on the pill for five minutes.

Review requests (added since this was opened, after the GitHub pulse landed on the Mac in #181): the pull requests your review is asked on stay at the top of the Activity tab, and a new request is news, told once.

Checks of your pull requests (added since, the other half of the Mac's pulse alerts): when the checks of one of your open pull requests end, red or green, it is news — on any project, not only the ones the panel lists. Same card as a merge; no screenshot of it yet.

Settings: switching GitHub on opens its setup under its line — the token, the permissions to grant, and a connection test that names the one that is missing.

All of these are the real island running on made-up data (dev/github-preview.html, see below), not mock-ups.

How to read it

Eleven commits, each of which builds:

Commit	What	Where
1	Keep the island on a whole pixel while it resizes	same commit as #55
2	Nothing in the views moves while folded or hidden	same commit as #56
3	Read GitHub from the Rust side	src-tauri/src/github.rs, github_detail.rs
4	The panel, its card and its news	src/views/github.ts, code.ts, palette.ts, style.css, and the wiring in island/, core/
5	GitHub's setup in the settings	src/settings/
6	A preview page	dev/github-preview.*
7	README and screenshots	windows/README.md, windows/screenshots/
8	News of a pull request somebody opened on one of your projects	src-tauri/src/github.rs, one line in views.ts and bridge.ts
9	A bell on each project, to choose which ones speak up	github.rs, settings.rs, src/views/github.ts
10	The pull requests waiting for your review, and news of a new request	github.rs, a section in src/views/github.ts
11	News when the checks of one of your pull requests end	github.rs

The first two are #55 and #56: the panel needs both (its scrolling lists are where the blur showed, and it adds endless animations). If you merge those first, they drop out of this diff.

How to try it

Without a token:

cd windows
npm install
npm run dev

then open http://127.0.0.1:1420/dev/github-preview.html — the links at the bottom go to each screen.

With a token: npm run tauri dev, Settings… → Integrations → GitHub, create a fine-grained token as described there, Test connection.

The rules of the house

• No new dependency: Cargo.toml, Cargo.lock, package.json and package-lock.json are unchanged.
• Settings: one new field, githubMuted (the projects kept quiet), defaulted when absent so an older settings.json still loads.
• Secrets: the token lives in the Windows Credential Manager through the existing secret_* commands. It is never written to disk or to the log, and never sent to the front — every request to GitHub is made by the Rust side, the front only asks whether a token exists.
• Read-only: a fine-grained token with Actions, Contents, Deployments, Issues and Pull requests on Read-only (Events is optional, for private activity). Coucou never writes to GitHub. A part the token cannot read says which permission it lacks.
• No telemetry, network only to what the user configured: api.github.com, and only once a token is saved and GitHub is switched on.
• 0 % CPU when hidden: with the island hidden, all of Coucou's processes used 94 ms of CPU over 60 s on a 20-core machine (dev build), a GitHub refresh included. See Windows: nothing in the views moves while the island is folded or hidden #56.
• Build: tsc --noEmit, vite build, cargo check pass; cargo test 61 passed (53 of them new, on the parsing and on what counts as news); cargo clippy shows nothing new.
• Docs: a GitHub section in windows/README.md. I left CHANGELOG.md to you.

Things you should know before merging

• The card is not the one in main. It replaces the GitHub card's content (figure, week, activity lines). It is the part most likely to be a matter of taste.
• Next to the Mac's pulse (GitHub pulse: open PRs, CI status and reviews in the notch #181, GitHub pill: catch fast CI runs, refresh on open #185): this panel reads GitHub through its own code and was written before the pulse. Review requests are the part of the pulse it lacked; a build that finishes between two looks was already caught, since a run is told apart by its id. The Mac's news of a pull request's checks turning red or green is here too since commit 11, with the pulse's own rule for a commit whose checks start and end between two looks.
• GitHub is asked more often: every 2 minutes instead of 5, and every 20 seconds for builds alone while one of them is running. Requests carry ETags, so unchanged answers do not count against the rate limit, and nothing is asked while Coucou is paused or GitHub is off.
• island.ts and views.ts gained three things a view can ask of Mochi through ViewActions: a tint (tintMochi), a state (look), and going to the news at hand (followNews). A click on Mochi goes to the news when there is some, and is the usual slap otherwise.
• The GitHub poller left integrations.rs for github.rs; the other pollers are untouched.

What I did not check

• Display scales other than 100 %.
• The news of a broken build and of a merged pull request were tested through the real event path with made-up events, and the detection is covered by unit tests, but I have not yet seen either fire from a real build or a real merge. The news of a pull request somebody opened is covered by a unit test and its query runs against the real API, but I have not yet seen it fire from a real pull request either. Muting a project is covered by a unit test for builds; I have not waited for real news on a muted project to see it stay quiet.
• Review requests: the query runs against the real API with my fine-grained token and answers without an error, but nobody is asking for my review right now, so the list and the news were only seen on the preview's data (?review, ?news=review&view=pill) and through the unit test. I have not checked what a classic token sees.
• Checks of your pull requests: the query answers without an error, but with my fine-grained token GitHub gives no roll-up for any of my 8 open pull requests (the log says 0 of 8 open pulls with checks) — the token has no Commit statuses permission, which the README now lists as optional. So this news is covered by a unit test only; I have not seen it fire.
• Every query was run against the real API on my own account; jumping from a review thread to its line in the diff was only exercised on the preview's data.