GitHub CLI alternative for Forgejo

If your team lives in gh today, plan the commands that matter before migration day.

CLI

What this solves

You are leaving GitHub or evaluating Forgejo and want a terminal workflow comparable to gh.

Best fit

Pull request review
Issue triage
Release automation
CI log inspection

How to think about it

Most teams do not need a one-for-one clone of every gh command. They need their frequent workflows covered: listing review work, opening a pull request, reading CI results, creating releases, and calling the forge API for the few cases that are unique to their process.

Migration inventory

# Build this from shell history, scripts, and CI jobs.
gh pr list        # map to pull request listing
gh pr view 42     # map to review details
gh run watch      # map to Actions run inspection
gh release create # map to release automation
gh api ...        # map to raw Forgejo API calls

Practical path

01 Inventory the gh commands your team uses weekly.
02 Map interactive review and release flows to fj.
03 Keep raw API scripting for edge cases while the team adjusts.

When to choose another path

Check scripts and aliases, not only commands people remember using.

Call out commands that depend on GitHub-only services before cutover.

Keep a short compatibility table in the migration plan.

Next resources

fj CLI

Product overview and install path.

CLI docs

Command documentation and examples.

Actions migration

Move CI workflows deliberately.

Tools hub

Calculators and planning tools.