Gitea Actions

Monitor your CI/CD pipelines without leaving your editor

A powerful extension that brings Gitea Actions directly into your editor. View workflow runs, stream logs in real-time, and manage secrets — all without switching to your browser.

Works with: VS Code, Cursor, VSCodium, Windsurf, and any editor supporting VS Code extensions.

Why Use This Extension?

• Stay in flow — No more context-switching to check if your build passed
• Real-time feedback — Watch logs stream live as your jobs run
• Full control — Manage secrets and variables right from your editor
• Universal compatibility — Works with VS Code, Cursor, VSCodium, and more

Features

Live Workflow Monitoring

See all your workflow runs at a glance with live status updates. Runs are organized by repository with clear visual indicators for success, failure, running, and queued states.

Real-Time Log Streaming

Click any running job to stream its logs directly in an editor tab. Logs auto-refresh until the job completes — no manual refreshing needed.

Step-by-Step Debugging

Drill down into individual steps to view their specific logs. Perfect for pinpointing exactly where a workflow failed.

Secrets & Variables Management

Create, update, and delete repository secrets and variables without leaving VS Code. Manage your CI/CD configuration in one place.

Smart Polling

The extension adapts its refresh rate based on activity:

• 15 seconds when workflows are running (configurable)
• 15 seconds when idle (configurable)

Targeted Refresh: Run status is always refreshed, but job and step details are only fetched for expanded runs (or runs that already have jobs loaded). Active expanded runs refresh job/step data every 5 seconds until completion (configurable).

Log Streaming: Job and step logs poll every 5 seconds while streaming (configurable).

Focus-Aware Polling: Polling pauses when the editor window is unfocused and all Gitea views are hidden, and resumes when you return.

Status Bar Integration

A subtle status bar indicator shows you the current state of your workflows at a glance.

Quick Start

1. Install

VS Code / Cursor / Windsurf:
Search for "Gitea Actions" in the Extensions panel, or get it from the VS Code Marketplace.

VSCodium / Gitpod / Theia:
Install from the Open VSX Registry.

2. Configure

1. Open Settings and set giteaActions.baseUrl to your Gitea instance
   (e.g., https://gitea.example.com)

2. Open the Gitea Actions panel in the activity bar

3. In the Settings section, click the pencil icon next to Token to set your Personal Access Token

4. Click Test Connection to verify everything works

That's it! Your repositories will appear automatically.

Workspace discovery supports both HTTP and SSH clone URLs: the extension matches your git remote host to the configured Gitea base URL, so repositories cloned via SSH (e.g. ssh://git@localhost:22/owner/repo.git) are recognized when the base URL is the same host (e.g. http://localhost:3000).

Tree Views

Workflow Runs

Shows your repositories with their recent workflow runs. The tree is organized as:

Repository
  └── Workflow Run [#123](https://github.com/tarkilhk/gitea-actions-vscode-plugin/issues/123)
        └── Job: build
              └── Step: Checkout
              └── Step: Build
              └── Step: Test

When you have a single repository open, it auto-expands for quick access.

Workflows

Groups runs by workflow name — useful when you want to see all runs of a specific workflow across your repositories.

Settings

Manage your extension configuration:

• Token — Set or clear your Personal Access Token
• Test Connection — Verify your Gitea connection
• Secrets — Manage encrypted repository secrets
• Variables — Manage plain-text configuration variables

Configuration

Discovery Modes

Tips & Tricks

• Expand runs on-demand — Jobs aren't fetched until you expand a run, keeping things fast
• Click any job to view its complete logs in an editor tab
• Click a specific step to view only that step's logs
• Click the status bar to quickly jump to the Gitea Actions panel
• Main status summary now shows failed workflows only (deduplicated by workflow ID, based on each workflow's latest run)

Steps and Gitea Limitations

Job steps (the list under each job) are unfortunately limited by Gitea's API:

1. Official API — The Gitea API schema includes a steps field on jobs, but Gitea has never implemented populating it — it always returns null. We still call it in case a future Gitea version starts returning steps.

2. Internal (web UI) API — The extension falls back to the same endpoint the Gitea web UI uses. Gitea only allows PAT access to this endpoint for public repos. For private repos the run page returns 404, so step details cannot be loaded.

Bottom line: If you see "Steps unavailable: Gitea does not expose step details for private repos", this is a Gitea limitation: step breakdown works for public repos only. Job logs still work via the official logs API for all repos — only the per-step breakdown is affected.

Workaround for older Gitea: If you're running Gitea 1.23 or earlier, steps should still work.

Diagnose Steps

If you're unsure why steps aren't loading, run "Gitea Actions: Diagnose Steps" from the Command Palette (Ctrl+Shift+P). It probes the official and internal APIs for a specific run and prints a detailed report to the Gitea Actions output channel, showing exactly which endpoint failed and why.

Security

Your Personal Access Token is stored securely using the editor's built-in SecretStorage API. It's never written to settings files, logs, or transmitted anywhere except to your Gitea instance.

Requirements

• Any compatible editor: VS Code 1.105+, Cursor, VSCodium, Windsurf, Gitpod, or Theia
• A Gitea instance with Actions enabled
• A Personal Access Token with appropriate permissions

Contributing

Contributions are welcome! Check out the GitHub repository to report issues or submit pull requests.

License

MIT — See LICENSE for details.

Enjoying this extension? Consider leaving a ⭐ on GitHub, or a review on the VS Code Marketplace or Open VSX Registry!