Revue Companion

Editor companions for Revue, the desktop app for reviewing pull requests on GitHub, Bitbucket Cloud and Forgejo: your repository's pull requests from Revue inside the editor, and the way back, with Revue opening a pull request in the editor window that has its branch.

Editor	Folder	Status
JetBrains IDEs (IntelliJ IDEA, Rider, PyCharm, WebStorm, GoLand…)	jetbrains/	On the JetBrains Marketplace as Revue Companion
VS Code (and Cursor, VSCodium, Windsurf…)	vscode/	Built, not released yet (Open VSX and the VS Code Marketplace)
Neovim	nvim/	Built, not released yet
Zed	zed/	Built, not released yet (Zed's extensions)

Every companion talks to Revue only through the revue command (see Revue's command line docs), so no sign-in tokens enter the editor. Revue must be installed.

Releases

Each companion has its own release workflow in Actions (release-jetbrains, release-vscode, release-nvim, release-zed), and its own tags (jetbrains-vX.Y.Z, vscode-vX.Y.Z, nvim-vX.Y.Z, zed-vX.Y.Z); each companion's README says what its workflow needs. For the JetBrains plugin: Actions → release-jetbrains → Run workflow, then pick whether to raise the patch, minor or major version, and the change notes (items separated by ;). It needs two repository secrets:

Secret	What
JETBRAINS_MARKETPLACE_TOKEN	JetBrains Marketplace token (plugins.jetbrains.com → profile → My Tokens)
RELEASE_TOKEN	Forgejo access token with write:repository and read:user, to push the release commit and tag as its owner

The Marketplace's first version is uploaded by hand.

License

MIT OR Apache-2.0, like Revue itself.