Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
07e5f19
feat(cmdutil): keep the API message of a failed page
q-horde Nov 8, 2026
896d02e
feat(gpg-key): add gpg-key list
q-horde Nov 8, 2026
32414b7
feat(gpg-key): add gpg-key add
q-horde Nov 8, 2026
2d6f63e
docs: document gpg-key list and add
q-horde Nov 8, 2026
64ada01
test(integration): add the GPG key fixture and the gpg-key test
q-horde Nov 16, 2026
e5ce2af
revert: drop the GPG key fixture and its integration test
q-horde Nov 16, 2026
7f053b7
feat(gpg-key): drop --signature from gpg-key add
q-horde Nov 16, 2026
13210f0
test(integration): list GPG keys against Copia
q-horde Nov 16, 2026
fd3281e
fix(cmdutil): bound the API message of an error response
q-horde Nov 16, 2026
5a5038b
fix(gpg-key): send only public key blocks and withhold quoted keys
q-horde Nov 16, 2026
2d42a23
Merge pull request #502 from qubernetic/develop
q-horde Nov 16, 2026
6c7c503
Merge pull request #488 from qubernetic/feature/482-gpg-key-list-add
q-horde Nov 16, 2026
1f3c97d
feat(gpg-key): add gpg-key delete
q-horde Nov 16, 2026
93de520
Merge pull request #503 from qubernetic/feature/483-gpg-key-delete
q-horde Nov 16, 2026
d7d3a89
feat(repo): add repo collaborator list and add
q-horde Nov 16, 2026
4bf1d8e
test(integration): check the collaborator permission route without th…
q-horde Nov 16, 2026
b31b684
fix(repo): drop the permission from repo collaborator list
q-horde Nov 16, 2026
0aa2fbe
Merge pull request #504 from qubernetic/feature/486-repo-collaborator…
q-horde Nov 16, 2026
84568f2
feat(repo): add repo collaborator remove
q-horde Nov 16, 2026
e05a0d0
Merge pull request #506 from qubernetic/feature/50-repo-collaborator-…
q-horde Nov 16, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Added

- `repo collaborator remove <login> --yes` removes a collaborator from a repository (`-R` or the current one); gh has no such command. Without `--yes` it fails with `--yes required when not running interactively` before anything else. It checks `GET /repos/{owner}/{repo}/collaborators/{login}` first, since Gitea answers 204 to a delete of a non-collaborator: a 404 fails with `<login> is not a collaborator of <owner>/<repo>`. Then it sends `DELETE /repos/{owner}/{repo}/collaborators/{login}` and prints `Removed <login> from <owner>/<repo>`. A login that is not a Gitea login fails before the request; Copia's other refusals are shown with the HTTP status and its message (#50)
- `repo collaborator list` (alias `ls`) and `repo collaborator add <login>` manage the collaborators of a repository (`-R` or the current one); gh has no such commands. `list` reads `GET /repos/{owner}/{repo}/collaborators` up to `-L/--limit` (default 30): the columns LOGIN and NAME, `--json` takes `login` and `full_name`, with `--jq` and `--template`; none prints `no collaborators found in <owner>/<repo>` on standard error, exit 0. It shows no permission: Copia answers Gitea's `GET /repos/{owner}/{repo}/collaborators/{login}/permission` with a plain-text `404 page not found` (the route is not registered). `add` sends `PUT /repos/{owner}/{repo}/collaborators/{login}` with `-p/--permission` `read`, `write` (the default, Gitea's) or `admin`, then `Added <login> to <owner>/<repo> with <permission> permission`, also when the user was a collaborator already (Gitea changes the permission). Any other permission, and a login that is not a Gitea login, fail before the request; an unknown user fails with `user <login> not found`, Copia's other refusals are shown with the HTTP status and its message (#486)
- `gpg-key delete <key-id>` deletes a GPG key from your Copia account, as in `gh`. The key is named by its GPG key ID, compared regardless of case, and looked up on every page of `GET /user/gpg_keys` (Gitea answers 204 to a delete of an unknown id); no match fails with `unable to delete GPG key <key-id>: either the GPG key is not found or it is not owned by you`, a match is deleted with `DELETE /user/gpg_keys/{id}`, then `GPG key <key-id> deleted from your account`. There is no prompt, so `-y/--yes` is required (`--yes required when not running interactively`). Copia's refusals are shown with the HTTP status and its message (#483)
- `gpg-key list` (alias `ls`) and `gpg-key add [<key-file>]` manage the GPG keys of your Copia account, as in `gh`. `list` reads every page of `GET /user/gpg_keys`: the columns EMAIL (the key's emails joined with `, `), KEY ID, PUBLIC KEY (cut in the middle on a terminal), ADDED and EXPIRES (`Never` or the date on a terminal, RFC 3339 without one); `--json` takes `id`, `key_id`, `primary_key_id`, `emails`, `public_key`, `created_at`, `expires_at`, `verified` and `can_sign`, with `--jq` and `--template`. No keys prints `no GPG keys present in the Copia account` on standard error, exit 0. `add` reads the armored key file, or standard input with `-` or without an argument when standard input is not a terminal, and sends it with `POST /user/gpg_keys`, then `GPG key added to your account`. Copia adds only a key whose email is a verified email of the account; its 404 for any other key is shown with a hint to add and verify that email (Copia has no `GET /user/gpg_key_token`, so Gitea's signature route and a `--signature` flag do not apply). A key Copia already has fails with `the key already exists in your account`; only public key blocks are sent: a private or secret key of any armored format (PGP, OpenSSH, PKCS#8, RSA, EC, DSA), also after a public block, is refused, and any other content fails with gh's hint that the key might not be ASCII-armored, both before any request. Copia's refusals are shown with the HTTP status and its message (cut to 512 bytes, read from at most 64 KiB of the response); a message that quotes the key, also re-wrapped or joined, is left out. gh's `-t/--title` is left out, since Gitea's GPG keys have no title (#482)
- `repo sync [-s/--source owner/repo] [-b/--branch branch] [--force]` syncs a branch of the local clone from a git remote, as `gh repo sync` does: the source is `--source` or the default repository (`-R`, `repo set-default`, else `origin`), the branch defaults to the source's default branch, `git fetch` gets the token only for an https remote on the configured host, and the branch is fast-forwarded (`merge --ff-only` when checked out, `branch --force` otherwise, created when missing). Diverging changes fail unless `--force` (`reset --hard`), and a dirty working tree is refused, both with gh's messages; success prints `Synced the "<branch>" branch from "<owner>/<repo>" to local repository`. `repo sync <owner/repo>` syncs a fork from its parent through `POST /repos/{owner}/{repo}/merge-upstream` fast-forward only; app.copia.io has no such route, so there it fails with `Copia does not offer fork sync through its API` (#45)
- `repo archive [<owner/repo>] --yes` and `repo unarchive [<owner/repo>] --yes` archive and unarchive the given repository, the current one or `-R`, as in `gh`: `PATCH /repos/{owner}/{repo}` with `archived`, then `Archived repository <owner>/<repo>` or `Unarchived repository <owner>/<repo>`. A repository already in that state gets `! Repository <owner>/<repo> is already archived` (or `is not archived`) on standard error, no change and exit 0; without `-y/--yes` both fail with `--yes required when not running interactively` before any API call. `repo view --json` gains the `archived` field (#462)
- `repo rename <new-name> --yes` renames the current repository or `-R`, as in `gh`: `PATCH /repos/{owner}/{repo}` with the new name, then `Renamed repository <owner>/<new-name>`. A name with `/` fails with gh's message and makes no API call; without `-y/--yes` it fails with `renaming <owner>/<repo> to <new-name> needs confirmation; use --yes to confirm`. Without `-R` the git remote that points at the old repository on the configured host (the `repo set-default` one first, then `origin`) gets the new name with `git remote set-url`, keeping its scheme, user, host and `.git` suffix, and `Updated the "<remote>" remote` is printed; when no remote matches or git fails, a warning goes to standard error and the command still succeeds (#461)
Expand Down
4 changes: 2 additions & 2 deletions CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,12 +85,12 @@ copia-cli/
Phase 1 (MVP): auth, repo list/view/clone, issue CRUD, pr CRUD, label list/create — **DONE**
Phase 2: release CRUD, repo create/delete/fork, pr review/diff/checkout, issue edit, Homebrew tap — **DONE**
Phase 3: `copia-cli api` escape hatch, search, orgs, notifications, `-R` flag, completion, Jekyll manual, AGPL license — **DONE**
Phase 4: ~~winget~~, ~~COPR~~, ~~AUR~~, ~~Snap~~, ~~OS keyring~~, ~~aliases~~, ~~browse~~, ~~status dashboard~~, ssh-key, pr checks, changelog, collaborators
Phase 4: ~~winget~~, ~~COPR~~, ~~AUR~~, ~~Snap~~, ~~OS keyring~~, ~~aliases~~, ~~browse~~, ~~status dashboard~~, gpg-key (list and add done; ssh-key dropped, Copia has SSH disabled), pr checks, changelog, collaborators

**Out of scope:** workflow/run, codespace, copilot, project, cache, GUI

## Reference Documentation

- `docs/api-reference.md` — Full Gitea API endpoint mapping with request/response examples
- `docs/authentication.md` — Auth methods, token generation, config file format, multi-instance setup
- `docs/parity.md` — Feature parity tracker against the Gitea 1.26 API (84 implementable: 76 implemented, 4 full, 4 partial; 13 impossible)
- `docs/parity.md` — Feature parity tracker against the Gitea 1.26 API (86 implementable: 81 implemented, 1 full, 4 partial; 15 impossible)
Loading
Loading