JetBrains IDEs 2024.1 or later

Pipeline Inbox for Forgejo and Gitea

A free CI run inbox in IntelliJ IDEA, PyCharm, WebStorm, Rider and the other JetBrains IDEs, for Forgejo Actions and Gitea Actions: the runs of every repository you have open, on Codeberg, gitea.com or your own server, in one IDE tool window, with their jobs and logs. A notification when yours finish. No AI features, no telemetry.

Get it on JetBrains Marketplace · reading is free, Pro has a 30-day trial

Comparing Forgejo Actions and Gitea Actions plugins for IntelliJ IDEA, PyCharm or Rider? See the options side by side.

Pull requests on Forgejo or Gitea waiting for your review, in the same IDE: our Forgejo and Gitea pull request plugin.

This plugin is not affiliated with, endorsed, sponsored, or approved by the Forgejo project, Codeberg e.V., or the Gitea project and its owners. Forgejo, Gitea and Codeberg are names of their respective owners.

Supported servers

Forgejo 16 or later (Codeberg, code.forgejo.org) and Gitea 1.25 or later (gitea.com). Older versions list runs but have no API for the jobs and logs of a run: the plugin says so, names the server's version and links the run's web page. What a server can do depends on its version, and the plugin shows only the buttons the server can do:

Re-run a run or one job: Forgejo 17, Gitea 1.26. Re-run only the failed jobs: Gitea 1.26 (Forgejo has no such API).
Cancel a run: Forgejo 16, Gitea 28.
Run a workflow by hand: Forgejo 13, Gitea 1.24.

As of October 28, 2026, Codeberg runs Forgejo 16, so re-running is not there yet; code.forgejo.org runs Forgejo 17.

Runs

Every Forgejo or Gitea repository in the IDE project together, read from its Git remotes (multi-repository projects too)
Or the 20 most recently updated repositories of their owners, or of your own
Filters: started by me, my current branch (with the runs of its open pull requests), failed
Each row: status, workflow, commit or pull request title, branch or pull request, who started it, what started it (pull request, schedule, by hand), how long it took and when; runs waiting for a maintainer to approve them are marked
For the repositories cloned in the IDE: a notification when a run you started finishes (without a token: the runs of your current branch), with a link to the log of the job that failed; the latest run of the current branch in the status bar

Jobs and logs

The jobs of a run with their status, attempt and duration
Job logs in a console viewer at the bottom, in the colours of the log, without the timestamp the runner puts on every line and without the group markers, searchable, following a running job as it writes

Acting

Re-run all jobs of a run, only the failed ones (Gitea), or one job, whose log follows the new attempt
Cancel a run that is still going
Run a workflow that has workflow_dispatch, on a branch or tag, with a field for each input its file declares (text, choice, checkbox, number), defaults filled in and the values remembered if you like; when the server refuses, the dialog stays open with its reason

Free and paid

Free: the list of runs, their jobs, job logs, notifications and the status bar. Paid (marked Pro in the plugin), with a 30-day free trial: re-run, cancel and run workflows. Licenses are sold through JetBrains Marketplace: US$1.50 a month or US$15 a year for individuals, US$3 a month or US$30 a year per user for organizations (Marketplace shows the price in your currency). Reading is free for everyone, so in a team only the people who re-run, cancel or start workflows from the IDE need a license. When the trial or a license ends, reading keeps working; only those actions lock.

Buying for a team: an organization license is managed in JetBrains Account, where an administrator assigns it to developers; the on-premises JetBrains License Server can serve it too. Pay by card or PayPal; for a purchase order or a bank transfer, ask for a quote with Get Quote on the plugin's Marketplace pricing page.

Install

Install it from JetBrains Marketplace, or in your IDE open Settings | Plugins | Marketplace and search for Pipeline Inbox for Forgejo and Gitea. Open Forgejo Actions in the right tool window bar: the repositories of this project are already in it.

Works with

Codeberg, recognised from the remote; gitea.com, code.forgejo.org and a server whose host name says forgejo or gitea are recognised too
Any number of other Forgejo or Gitea servers in Settings | Tools | Pipeline Inbox for Forgejo and Gitea, also one that runs below a path, each with its own token
HTTPS and SSH remotes
The IDE's proxy settings (including proxy authentication) and trusted certificates, for self-signed or company certificates
Every JetBrains IDE with Git support: IntelliJ IDEA, Rider, PyCharm, WebStorm, GoLand, PhpStorm, CLion, RubyMine and others, and Android Studio Koala (2024.1.1) and later

Token

On Forgejo, public repositories can be read without a token: runs, jobs and logs. Gitea asks for a token even then. For private repositories and "started by me", create an access token on your server (Settings | Applications on the web, /user/settings/applications) with the scopes write:repository and read:user (to re-run, cancel and run; choose them from the start to try Pro), or read:repository and read:user to read only. Enter it in Settings | Tools | Pipeline Inbox for Forgejo and Gitea, for each server: each token is kept in the IDE's password safe and sent only to its own server.

Errors explained

No AI features, no cloud of ours

The plugin talks only to Codeberg, to the servers in its settings and, without a token, to gitea.com, code.forgejo.org or a server your Git remote points at whose host name says forgejo or gitea. Redirects to other hosts are not followed. Your code and logs are not sent to any AI service or to any server of ours, and there is no telemetry.

日本語

IDE の言語が日本語のとき、画面の文言は日本語で表示されます（サーバーから届くメッセージやワークフロー名はそのまま）。お問い合わせは日本語でも受け付けます。日本語の説明