• go-v0.2.0 b670adc066

    go-v0.2.0
    All checks were successful
    Go build / build (fj, darwin) (push) Successful in 40s
    Go build / build (fj, linux) (push) Successful in 41s
    Go build / build (fj.exe, windows) (push) Successful in 41s
    Release binaries / upload (fj-darwin-amd64, darwin) (release) Successful in 37s
    Release binaries / upload (fj-linux-amd64, linux) (release) Successful in 32s
    Release binaries / upload (fj-windows-amd64.exe, windows) (release) Successful in 33s
    Stable

    techwritescode released this 2026-09-10 13:12:41 +00:00 | 0 commits to main since this release

    • fj actions -- Forgejo Actions (CI) support: run list/view/jobs/logs/cancel/delete/browse, artifact list/download/delete, dispatch. run logs --follow tails a running job's log in real time.
    • fj repo create OWNER/NAME (or HOST/OWNER/NAME) -- create a repo under an org, not just your own account.
    • fj repo sync -- git pull, retried once on failure (works around a reauth quirk over HTTPS).
    • Fixed: a git remote on a custom SSH port no longer leaks that port into HTTP(S) API requests.
    • CI now cross-compiles linux/windows/darwin from a single runner and attaches the binaries to releases automatically.
    Downloads
  • go-v0.1.0 fa6c97d620

    go-v0.1.0
    All checks were successful
    Go build / build (fj, darwin) (push) Successful in 40s
    Go build / build (fj, linux) (push) Successful in 37s
    Go build / build (fj.exe, windows) (push) Successful in 39s
    Stable

    techwritescode released this 2026-09-02 16:34:31 +00:00 | 4 commits to main since this release

    First release of the Go rewrite (fj is a personal fork of forgejo-cli, mid-port from Rust to Go). Not yet at feature parity with the old Rust CLI.

    Implemented:

    • auth (token and OAuth PKCE login)
    • config
    • whoami
    • repo (full parity with the old Rust repo.rs)
    • issue
    • org
    • release (create/edit/delete/list/view/browse, plus asset upload/download)

    Fixed in this release:

    • A git remote on a custom SSH port (e.g. ssh://git@host:222/owner/repo.git) no longer leaks that port into HTTP(S) API requests.

    pr is next.

    Downloads