chore(metadata): point package metadata at fork (FJ-17) #15

Merged

David merged 2 commits from chore/repoint-package-metadata-fork-fj-17 into main

2026-05-25 18:28:02 +02:00

David commented

2026-05-25 17:25:04 +02:00

Owner

Repoints the package-metadata pointers from the upstream Codeberg repository to the fork's canonical home, https://dev.a8n.run/pandoras-box/forgejo-cli. Resolves FJ-17.

The fork is published from the origin remote, but the three crate manifests advertised the upstream Codeberg URL in their repository field and the Nix flake advertised it as homepage. Tooling that reads these fields (cargo metadata, crate tooling, the Nix derivation meta) therefore pointed downstream consumers at an upstream we cannot contribute to.

Changes

crates/fj/Cargo.toml, crates/fj-core/Cargo.toml, crates/fj-client/Cargo.toml: repository -> https://dev.a8n.run/pandoras-box/forgejo-cli (trailing slash dropped for a bare repo URL).
flake.nix: homepage -> https://dev.a8n.run/pandoras-box/forgejo-cli.

Out of scope (intentionally unchanged)

Fork-attribution prose in README.md / CLAUDE.md, the upstream wiki/install links in README.md (the fork hosts no wiki of its own), and incidental codeberg.org references (crates/fj/src/actions.rs, crates/fj/src/repo.rs, the codeberg.org host-to-client-ID mapping in crates/fj-client/src/client_info.rs).

Verification

No remaining forgejo-contrib/forgejo-cli reference in any Cargo.toml or flake.nix.
just check (fmt + clippy + build + tests + builder-stage Docker compile) passes.

Repoints the package-metadata pointers from the upstream Codeberg repository to the fork's canonical home, `https://dev.a8n.run/pandoras-box/forgejo-cli`. Resolves FJ-17. The fork is published from the `origin` remote, but the three crate manifests advertised the upstream Codeberg URL in their `repository` field and the Nix flake advertised it as `homepage`. Tooling that reads these fields (`cargo metadata`, crate tooling, the Nix derivation `meta`) therefore pointed downstream consumers at an upstream we cannot contribute to. ## Changes - `crates/fj/Cargo.toml`, `crates/fj-core/Cargo.toml`, `crates/fj-client/Cargo.toml`: `repository` -> `https://dev.a8n.run/pandoras-box/forgejo-cli` (trailing slash dropped for a bare repo URL). - `flake.nix`: `homepage` -> `https://dev.a8n.run/pandoras-box/forgejo-cli`. ## Out of scope (intentionally unchanged) Fork-attribution prose in `README.md` / `CLAUDE.md`, the upstream wiki/install links in `README.md` (the fork hosts no wiki of its own), and incidental `codeberg.org` references (`crates/fj/src/actions.rs`, `crates/fj/src/repo.rs`, the `codeberg.org` host-to-client-ID mapping in `crates/fj-client/src/client_info.rs`). ## Verification - No remaining `forgejo-contrib/forgejo-cli` reference in any `Cargo.toml` or `flake.nix`. - `just check` (fmt + clippy + build + tests + builder-stage Docker compile) passes.

David added 1 commit

2026-05-25 17:25:04 +02:00

chore(metadata): repoint package metadata at fork (FJ-17)

Check / fmt + clippy + build + tests (pull_request) Successful in 35s

Details

508bd68db1

The three crate manifests advertised the upstream Codeberg repository in their `repository` field and the Nix flake advertised it as `homepage`, even though the fork is published from `https://dev.a8n.run/pandoras-box/forgejo-cli`. Point all four package-metadata fields at the fork so `cargo metadata`, crate tooling, and the Nix derivation `meta` resolve to the fork we publish from. Prose attribution, the upstream wiki/install links in README, and incidental `codeberg.org` references are intentionally left untouched.

#FJ-17 State Done

David added 1 commit

2026-05-25 18:27:51 +02:00

Merge branch 'main' into chore/repoint-package-metadata-fork-fj-17

Create release / Create release from merged PR (pull_request) Has been skipped

Details

Check / fmt + clippy + build + tests (pull_request) Successful in 1m27s

Details

8d05a1a2d3