Editors: mark a pull request's files viewed (`--review` says which, `--viewed` marks them) #78

New issue

Closed

opened 2026-11-12 23:18:47 +01:00 by thatrichan · 0 comments

thatrichan commented

2026-11-12 23:18:47 +01:00

Owner

The JetBrains companion's review (its diff viewer and the Revue Review tool window) should let you mark files viewed, as Revue's own Files tab does (the checkbox, v, 3/12 viewed), sharing the same marks: synced to GitHub where syncs_viewed, kept by Revue for Bitbucket and Forgejo. The command line can't tell or change them yet, and companions only talk to Revue through it.

What the companion needs

--review <url> says each file's mark: "viewed": true|false on every entry of files.
revue --viewed <url> --file <path> [--off] marks the file viewed (or, with --off, not), the same way the Files tab's checkbox does, and answers {"viewed": true|false}. Exit codes as the other review questions (not running, not signed in…), and --headless like them.
editor 7 in revue --version once both are in, so a companion knows to offer it. (The companion's code already expects these at editor 7, under the name REVIEW_EXTRAS, and shows nothing until a Revue says so.)
docs/command-line.md, "Reviewing from an editor": both documented.

What the companion does with it

A checkbox per file in the Revue Review tool window's file tree (built, hidden until editor 7).
Mark Viewed in the diff viewer's toolbar, and a shortcut, marking the file shown and moving to the next unviewed one, as v does in Revue.
Viewed files dimmed in the tree.

Related asks for the same editor 7, to file separately if wanted: reactions on review comments (reactions in --review, --react), and who can be @-mentioned (mentionable in --review).

The JetBrains companion's review (its diff viewer and the **Revue Review** tool window) should let you mark files viewed, as Revue's own **Files** tab does (the checkbox, <kbd>v</kbd>, **3/12 viewed**), sharing the same marks: synced to GitHub where `syncs_viewed`, kept by Revue for Bitbucket and Forgejo. The command line can't tell or change them yet, and companions only talk to Revue through it. ## What the companion needs 1. **`--review <url>`** says each file's mark: `"viewed": true|false` on every entry of `files`. 2. **`revue --viewed <url> --file <path> [--off]`** marks the file viewed (or, with `--off`, not), the same way the Files tab's checkbox does, and answers `{"viewed": true|false}`. Exit codes as the other review questions (not running, not signed in…), and `--headless` like them. 3. **`editor 7`** in `revue --version` once both are in, so a companion knows to offer it. (The companion's code already expects these at `editor 7`, under the name `REVIEW_EXTRAS`, and shows nothing until a Revue says so.) 4. `docs/command-line.md`, "Reviewing from an editor": both documented. ## What the companion does with it - A checkbox per file in the Revue Review tool window's file tree (built, hidden until `editor 7`). - **Mark Viewed** in the diff viewer's toolbar, and a shortcut, marking the file shown and moving to the next unviewed one, as <kbd>v</kbd> does in Revue. - Viewed files dimmed in the tree. Related asks for the same `editor 7`, to file separately if wanted: reactions on review comments (`reactions` in `--review`, `--react`), and who can be @-mentioned (`mentionable` in `--review`).

thatrichan referenced this issue from a commit

2026-11-12 23:36:46 +01:00

Editors: mark a pull request's files viewed from your code editor

thatrichan closed this issue

2026-11-12 23:36:46 +01:00

thatrichan referenced this issue from a commit

2026-11-13 00:41:54 +01:00

JetBrains: Mark Viewed in the review's diff, going on to the next file not viewed

thatrichan referenced this issue

2026-11-13 00:45:40 +01:00

Editors: reactions on review comments, and who can be @-mentioned, in --review #79

thatrichan referenced this issue from thatrichan/revue-companion