Forgejo VS Code Extension

Browse Pull Requests, Issues, and Actions from Forgejo, Gitea, and Codeberg directly in VS Code.

Install

Install from VS Code Marketplace -- or search for "Forgejo Integration" in the Extensions panel (Ctrl+Shift+X).

Install from Open VSX -- for VSCodium and other compatible editors.

Quick Start

1. Open a folder containing a Forgejo, Codeberg, or Gitea git repository
2. Click the Forgejo icon in the Activity Bar (sidebar)
3. Done! Your PRs and Issues appear automatically

For private repositories, add a Personal Access Token.

News

Next version

• Safer git remote detection: the extension now separates repository identity from instance resolution. HTTP(S) remotes still support zero-config detection, while SSH remotes no longer guess a Forgejo web/API URL from the git transport. If you're using SSH remotes with a self-hosted instance, configure the Forgejo instance explicitly for the most reliable matching.

Features

Pull Requests

• Browse PRs grouped by state (Open, Draft, Merged, Closed)
• View file changes directly in VS Code's diff editor
• Add inline review comments on PR diffs
• Create new pull requests from within VS Code
• Merge PRs with multiple strategies (merge, squash, rebase)
• Close PRs directly from the sidebar
• Rich detail view showing description, comments, CI status, and timeline

Issues

• Browse issues with full details and comments
• Create new issues from within VS Code
• Rich detail view with comment history and timeline events

Actions / CI

• Monitor CI/CD workflow runs in a 3-level tree view (Run > Job > Step)
• View job logs directly in the editor
• Re-run failed workflows
• Clickable CI status links in PR detail views

Multi-Instance & Auto-Detection

• Connect to multiple Forgejo servers simultaneously
• Auto-detect instance from your git remote
• Select preferred remote when multiple remotes exist
• Built-in diagnostics to troubleshoot connection issues

Browser Integration

• Open any PR, Issue, or Action in your browser with one click

Supported Platforms

• Codeberg
• Self-hosted Forgejo instances
• Gitea instances (compatible API)

Setting Up Authentication

Authentication is optional for public repositories but required for private repos.

Step 1: Create a Personal Access Token (PAT)

On Codeberg

1. Go to codeberg.org/user/settings/applications
2. Under "Manage Access Tokens", click Generate New Token
3. Enter a name (e.g., "VS Code Extension")
4. Select permissions:
   • read:repository - Browse repository files and pull requests (required)
   • read:issues - Browse issues (required)
   • write:repository - Merge PRs, close Issues (optional)
5. Click Generate Token
6. Copy the token immediately - you won't see it again!

On Self-Hosted Forgejo

1. Go to https://your-forgejo-instance.com/user/settings/applications
2. Follow the same steps as Codeberg above

Step 2: Add the Token to VS Code

Option A: Using Command Palette (Recommended)

1. Press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac)
2. Type "Forgejo: Add Instance"
3. Enter your instance URL (e.g., https://codeberg.org)
4. Enter a friendly name (e.g., "Codeberg")
5. Paste your token when prompted
6. Click Test Connection to verify

Option B: Using Settings UI

1. Open Settings: Ctrl+, (Windows/Linux) or Cmd+, (Mac)
2. Search for "forgejo"
3. Click Edit in settings.json under "Forgejo: Instances"
4. Add your instance configuration

Multiple Instances

You can connect to multiple Forgejo servers:

1. Run "Forgejo: Manage Instances" from Command Palette
2. Add additional instances with their own tokens
3. The extension will match repositories to the correct instance automatically

Usage

Viewing Pull Requests

1. Click the Forgejo icon in the Activity Bar
2. Expand the Pull Requests section
3. Click a PR to see its files
4. Click a file to view the diff

PR Actions

Right-click on a PR for options:

• View PR Details - See full description and comments
• Open PR in Browser - Open on Forgejo website
• Merge PR - Merge with options (merge commit, squash, rebase)
• Close PR - Close without merging

Viewing Issues

1. Expand the Issues section in the Forgejo view
2. Click an issue to see full details, comments, and timeline
3. Right-click to open in browser
4. Use the + button in the Issues title bar to create a new issue

Monitoring Actions / CI

1. Expand the Actions section in the Forgejo view
2. See workflow runs with their status (success, failure, running)
3. Expand a run to see individual jobs and steps
4. Click a step to view its logs in the editor
5. Right-click a run or job to re-run the workflow

Commands

Open Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and type "Forgejo":

Command	Description
Forgejo: Add Instance	Add a new Forgejo server
Forgejo: Manage Instances	View and edit configured servers
Forgejo: Create Pull Request	Create a new PR from the current branch
Forgejo: Create Issue	Create a new issue
Forgejo: Refresh Pull Requests	Reload PR list
Forgejo: Refresh Issues	Reload Issue list
Forgejo: Refresh Actions	Reload Actions list
Forgejo: Select Git Remote	Choose which git remote to use
Forgejo: Show Diagnostics	Debug connection issues
Forgejo: Show Output Channel	View extension logs

Configuration

Setting	Default	Description
forgejo.autoDetectFromRemote	true	Auto-detect instance from git remote
forgejo.preferredRemote	""	Preferred git remote name (default: auto-detect, falls back to origin)
forgejo.debug	false	Enable debug logging
forgejo.showFileStatusNotifications	true	Show notifications for added/deleted files

Troubleshooting

"No Forgejo configuration found"

• Make sure you're in a workspace with a git repository
• Check that you have a git remote configured (git remote -v)
• Try running "Forgejo: Add Instance" to manually configure

PRs or Issues not loading

1. Run "Forgejo: Show Diagnostics" to check connection status
2. Verify your token is valid and has correct permissions
3. Check the Output channel: "Forgejo: Show Output Channel"

Authentication errors

1. Regenerate your token on the Forgejo website
2. Run "Forgejo: Manage Instances" to update the token
3. Make sure the token has read:repository and read:issues scopes

Git remote not detected

The extension looks for the origin remote by default (configurable via forgejo.preferredRemote). Supported URL formats:

• HTTPS: https://codeberg.org/owner/repo.git
• SSH: git@codeberg.org:owner/repo.git
• SSH protocol: ssh://git@codeberg.org/owner/repo.git

Feedback & Issues

Found a bug or have a feature request? Please open an issue on the Codeberg repository.

Acknowledgments

• Forgejo - The self-hosted Git service this extension supports
• Codeberg - For hosting Forgejo and being a great community
• VS Code Extension API - For making this possible