repo edit: add command to update repo description, visibility, and other settings #27

okdas commented 2026年03月29日 18:49:40 +02:00

Summary

There's no repo edit command to update repository settings (description, visibility, etc.) after creation.

Current behavior

$ fj repo --help
Commands:
 create, fork, migrate, view, readme, clone, star, unstar, delete, browse, labels

No edit or update subcommand for repos.

Expected behavior

A repo edit command, similar to how issue edit, release edit, and org edit already work:

fj repo edit owner/repo --description "New description"
fj repo edit owner/repo --private false

Context

The edit pattern is well-established in the codebase:

• issue edit uses EditIssueOption + api.issue_edit_issue()
• release edit uses EditReleaseOption + api.repo_edit_release()
• org edit uses EditOrgOption + api.org_edit()

For repos, neither EditRepoOption nor a repo_edit() API method appear to be used. The Forgejo API does support PATCH /api/v1/repos/{owner}/{repo} — the forgejo-api crate may need to expose this type first.

Use case

After creating a repo (especially via CLI), there's no way to set/update the description without going to the web UI.

## Summary There's no `repo edit` command to update repository settings (description, visibility, etc.) after creation. ## Current behavior ``` $ fj repo --help Commands: create, fork, migrate, view, readme, clone, star, unstar, delete, browse, labels ``` No `edit` or `update` subcommand for repos. ## Expected behavior A `repo edit` command, similar to how `issue edit`, `release edit`, and `org edit` already work: ``` fj repo edit owner/repo --description "New description" fj repo edit owner/repo --private false ``` ## Context The edit pattern is well-established in the codebase: - `issue edit` uses `EditIssueOption` + `api.issue_edit_issue()` - `release edit` uses `EditReleaseOption` + `api.repo_edit_release()` - `org edit` uses `EditOrgOption` + `api.org_edit()` For repos, neither `EditRepoOption` nor a `repo_edit()` API method appear to be used. The Forgejo API does support `PATCH /api/v1/repos/{owner}/{repo}` — the forgejo-api crate may need to expose this type first. ## Use case After creating a repo (especially via CLI), there's no way to set/update the description without going to the web UI.

okdas commented 2026年03月29日 18:56:23 +02:00

Confirmed: the Forgejo API fully supports this via PATCH /api/v1/repos/{owner}/{repo} (operationId: repoEdit).

The EditRepoOption schema includes: description, name, private, archived, default_branch, has_issues, has_wiki, has_pull_requests, has_projects, has_packages, has_actions, has_releases, website, template, and many merge-related settings.

The forgejo-api Rust crate would need to expose this type (or it may already under a different name).

Confirmed: the Forgejo API fully supports this via `PATCH /api/v1/repos/{owner}/{repo}` (operationId: `repoEdit`). The `EditRepoOption` schema includes: `description`, `name`, `private`, `archived`, `default_branch`, `has_issues`, `has_wiki`, `has_pull_requests`, `has_projects`, `has_packages`, `has_actions`, `has_releases`, `website`, `template`, and many merge-related settings. The forgejo-api Rust crate would need to expose this type (or it may already under a different name).

stalecontext commented 2026年03月30日 20:03:55 +02:00

Going to do automated test suite before handling this, but will get to it after the next release

Going to do automated test suite before handling this, but will get to it after the next release