CLI
What this solves
You want to keep repository work in the shell while using Forgejo as the source of truth.
Terminal workflow for Forgejo
A good terminal workflow should shorten the path from clone to review to release.
Best fit
- Reviewing changes from a clone
- Following CI from the terminal
- Shipping releases without context switching
How to think about it
The terminal works best when the current git checkout gives enough context for the CLI to infer the forge, repository, and branch. That keeps the common workflow short while still allowing explicit flags in scripts and runbooks.
From branch to review
git switch -c fix/login-timeout
# edit, test, commit
git push -u origin fix/login-timeout
fj pr create --title "Fix login timeout" --body "Keeps sessions alive during slow OIDC redirects."Practical path
- 01 Let fj infer the repository from git remotes.
- 02 Use PR, issue, run, and release commands for daily work.
- 03 Link command docs from team runbooks so workflows are discoverable.
When to choose another path
Use explicit repository flags in shared scripts.
Make CI status visible before review approval.
Link the team runbook to the exact commands people should use.
Next resources
Related reading
Forgejo CLI for issues, pull requests, and releases
Use fj as a Forgejo CLI for issues, pull requests, releases, and Actions logs, and script the parts of your day that never needed a browser.
GitHub CLI alternative for Forgejo
Moving off gh? Map the GitHub CLI commands your team runs every day onto fj, so daily repository work still feels familiar after the switch to Forgejo.
Automating Forgejo with fj, Actions, and the API
Automate Forgejo with fj, Actions, and API calls: schedule routine jobs, wire repository hooks, handle secrets, and cut releases without touching the UI.