Working your Forgejo forge

Drive Forgejo from the terminal with fj: reviews, releases, and scripting.

• 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.
• CLI for Gitea and Forgejo-compatible hosts Use fj as your CLI for Gitea and Forgejo-compatible hosts: check what your host supports, then run issues, pull requests, and releases from the terminal.
• 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.
• Terminal workflow for Forgejo Build a terminal-first Forgejo workflow that carries a change from branch to review to release without leaving the shell, using fj and Forgejo Actions.

Publish static sites from a Forgejo repository, framework by framework.

• Deploy Astro to Forgejo Pages Deploy an Astro site with Forgejo Actions and Fjord Pages: install dependencies, build to dist, and publish the static output straight from a workflow.
• Deploy Hugo to Forgejo Pages Deploy a Hugo site from Forgejo Actions to Fjord Pages: pin the Hugo version, build to public, and publish the generated output on every push.
• Deploy MkDocs to Forgejo Pages Publish MkDocs documentation with Forgejo Actions and Fjord Pages: build the site from the repository and ship the exact generated output.
• Deploy Vite to Forgejo Pages Deploy a Vite static app to Fjord Pages from Forgejo Actions, with build output, workflow permissions and deploy steps spelled out.
• Custom domains for Forgejo Pages Plan custom domains for Forgejo Pages sites, including DNS records, HTTPS expectations, verification steps and when to keep a default domain.

Port GitHub Actions workflows to Forgejo Actions, step by step.

• GitHub Actions compatibility in Forgejo Understand what usually ports from GitHub Actions to Forgejo Actions, what needs testing, and how to plan a staged workflow migration.
• Replace checkout in Forgejo Actions Replace checkout steps when moving GitHub Actions workflows to Forgejo Actions, including repository URLs, tokens and reusable workflow caveats.
• Replace upload-artifact in Forgejo Actions Replace GitHub upload-artifact and download-artifact steps for Forgejo Actions with Fjord-compatible artifact storage patterns.
• Cache dependencies in Forgejo Actions Use dependency caches deliberately when porting Node, Python, Go, Rust, and Docker workflows to Forgejo Actions.
• Docker builds in Forgejo Actions Plan Docker image builds on Forgejo Actions runners, including cache behavior, registry login, secrets and when dedicated runners help.

Review, triage, and watch CI from Fjord Mobile, including a forge you host.

• Forgejo mobile app for iPhone and iPad Use Fjord Mobile as a native companion for Forgejo pull requests, issues, notifications and checks across managed or self-hosted forges.
• Self-hosted Forgejo mobile Connect mobile workflows to self-hosted Forgejo or a managed Fjord instance, with direct app access and practical review limits.
• Review Forgejo pull requests on iPhone Review Forgejo pull requests from iPhone with Fjord Mobile, including diffs, checks, approvals and when to switch back to the web UI.
• Forgejo mobile notifications Use mobile notifications for Forgejo pull requests, checks, reviews and repository activity, with setup steps and signal-control tips.