rasso/forgejo-publish
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
2 commits 1 branch 0 tags 60 KiB
  • TypeScript 88.9%
  • JavaScript 6.4%
  • Shell 4.7%
Find a file
Exact
Rasso Hilber b8c19c9678 Make extension standalone and host-agnostic 
- Publish via Forgejo API + git instead of the forgejo-publish script
- Ask for host on first run, token stored in SecretStorage
- Add install-extension script
2026-10-21 18:15:16 +02:00
.vscode VS Code command to publish repos to git.rassohilber.com via forgejo-publish 2026-10-21 17:43:15 +02:00
scripts Make extension standalone and host-agnostic 2026-10-21 18:15:16 +02:00
src Make extension standalone and host-agnostic 2026-10-21 18:15:16 +02:00
.gitignore VS Code command to publish repos to git.rassohilber.com via forgejo-publish 2026-10-21 17:43:15 +02:00
.npmrc VS Code command to publish repos to git.rassohilber.com via forgejo-publish 2026-10-21 17:43:15 +02:00
.vscode-test.mjs VS Code command to publish repos to git.rassohilber.com via forgejo-publish 2026-10-21 17:43:15 +02:00
.vscodeignore VS Code command to publish repos to git.rassohilber.com via forgejo-publish 2026-10-21 17:43:15 +02:00
CHANGELOG.md VS Code command to publish repos to git.rassohilber.com via forgejo-publish 2026-10-21 17:43:15 +02:00
eslint.config.mjs VS Code command to publish repos to git.rassohilber.com via forgejo-publish 2026-10-21 17:43:15 +02:00
package.json Make extension standalone and host-agnostic 2026-10-21 18:15:16 +02:00
pnpm-lock.yaml VS Code command to publish repos to git.rassohilber.com via forgejo-publish 2026-10-21 17:43:15 +02:00
README.md Make extension standalone and host-agnostic 2026-10-21 18:15:16 +02:00
tsconfig.json VS Code command to publish repos to git.rassohilber.com via forgejo-publish 2026-10-21 17:43:15 +02:00

README.md

Forgejo Publish

Adds Forgejo: Publish to Forgejo to the command palette, next to VS Code's "Publish to GitHub".

It asks for private/public, then: creates the repo on your Forgejo instance (or reuses an existing one with the same name), adds a remote (origin, or forgejo if origin is taken), pushes the current branch with upstream tracking and opens the repo in the browser.

Setup

On first run it asks for:

  1. The Forgejo host, e.g. git.example.com
  2. An access token (create one at https://<host>/user/settings/applications, scopes write:repository and write:user). Stored in the OS keychain via VS Code's SecretStorage, never in settings. A rejected token is removed, so the next run asks again.

The token is only used for the first push. Later pushes use your normal git credentials.

Build and install:

pnpm run install-extension

Then run "Developer: Reload Window".

Settings

  • forgejoPublish.host: Forgejo host to publish to (clear it to be asked again)