Tycho module: pull requests, issues and mirrors on Forgejo, GitHub, GitLab, Bitbucket
  • TypeScript 99.4%
  • JavaScript 0.6%
Find a file
Olivier d024e9879a chore: initial import
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 18:20:59 +01:00
src chore: initial import 2026-11-06 18:20:59 +01:00
tests chore: initial import 2026-11-06 18:20:59 +01:00
.gitignore chore: initial import 2026-11-06 18:20:59 +01:00
bun.lock chore: initial import 2026-11-06 18:20:59 +01:00
index.js chore: initial import 2026-11-06 18:20:59 +01:00
LICENSE chore: initial import 2026-11-06 18:20:59 +01:00
package.json chore: initial import 2026-11-06 18:20:59 +01:00
README.fr.md chore: initial import 2026-11-06 18:20:59 +01:00
README.md chore: initial import 2026-11-06 18:20:59 +01:00
tsconfig.json chore: initial import 2026-11-06 18:20:59 +01:00

🇫🇷 Version française

Tycho Forge

@tycho/forge is the Tycho module behind tycho forge. It gives one vocabulary for pull requests, repositories, issues, CI workflows and mirrors across Forgejo/Gitea, GitHub, GitLab and Bitbucket. The forge is detected from the origin remote of the current repository; when there is no remote, the primary forge chosen during tycho forge setup is used. --forge=forgejo|github|gitlab|bitbucket overrides the detection. For the overall picture, see the Tycho core README.

flowchart TD
    CLI["tycho forge &lt;command&gt;"] --> Resolver["ForgeContextResolver\n(origin remote, config or --forge)"]
    Resolver -- "git.qtrn.io / codeberg.org / Gitea" --> FJ["ForgejoDriver\n(tea CLI + REST API v1)"]
    Resolver -- "github.com" --> GH["GitHubDriver\n(gh CLI)"]
    Resolver -- "gitlab.com / self-hosted" --> GL["GitLabDriver\n(glab CLI)"]
    Resolver -- "bitbucket.org" --> BB["BitbucketDriver\n(REST API v2)"]
    FJ & GH & GL & BB -. implement .-> Port["GitForgeDriver interface"]

Install

tycho module add forge

The GitHub and GitLab drivers rely on the gh and glab CLIs; the Forgejo driver uses tea when present, otherwise the REST API with a token (FORGEJO_TOKEN or tycho forge setup). Bitbucket uses BITBUCKET_APP_PASSWORD.

Usage

tycho forge setup                                  # choose the primary forge (also: config)
tycho forge pr list [--state=open|closed|all]      # list pull/merge requests (alias: mr)
tycho forge pr view <number>
tycho forge pr create --title <t> [--body <b>] [--base <branch>]
tycho forge pr checkout <number>
tycho forge pr merge <number> [--squash|--rebase|--merge]
tycho forge repo view
tycho forge repo clone <target> [destination]
tycho forge repo create <name> [--public] [--org <org>] [--push] [--gitflow]
tycho forge issue list [--state open|closed|all]   # Forgejo only for now
tycho forge issue create --title <t> [--body <md>] [--label a,b] [--milestone <title>]
tycho forge issue import <roadmap.json> [--dry-run]
tycho forge action list                            # workflow templates (alias: workflow)
tycho forge action add container-build             # generate an OCI build workflow
tycho forge auth status
tycho forge whoami
tycho forge mirror status                          # show configured remotes
tycho forge mirror sync [remote]                   # push branches and tags (default remote: github)
tycho forge status                                 # standard git commands are passed to git

Any other command is passed through to the forge's native CLI (or to git).

Status

Functional. Issue commands (issue list|create|import) are implemented by the Forgejo driver only; other drivers report that they are not supported yet.

Licence

AGPL-3.0-only, © Quatrain Technologies. Source: https://git.qtrn.io/tycho/tycho-forge