Back to Codeberg

Ability to update repo description? #345

forgejo-contrib-forgejo-cli-issues-345.md

latest10.8 KB
Original Source

forgejo-contrib/forgejo-cli

Watch20

Star402

Fork

You've already forked forgejo-cli

51

CodeIssues 44Pull requests 8Releases 11Packages 2WikiActivity

Ability to update repo description? #345

New issue

Closed

opened 2026-03-03 20:45:49 +01:00 by xiaoshihou · 3 comments

xiaoshihou commented 2026-03-03 20:45:49 +01:00

Copy link

Like

shell
hut git update <repo> -d <desc>
glab repo update my-project --description "This project is cool."

I use many remotes for all my public work, and I'd like to keep them in sync and publicly available.

Thanks!

Like shell hut git update \<repo\> -d \<desc\> glab repo update my-project --description "This project is cool." I use many remotes for all my public work, and I'd like to keep them in sync and publicly available. Thanks!

LordMZTE commented 2026-03-09 19:52:40 +01:00

Collaborator

Copy link

I think the best way to implement this would be a command corresponding to the PATCH /repos/{owner}/{repo} endpoint. The problem here is that this allows us to edit a grand total of
34 different properties for a repository. In similar commands, we have a flag for each property,
though I'm not sure if that wouldn't be a little much here. Should I go for that, or do we have a
better idea here?

I think the best way to implement this would be a command corresponding to the PATCH /repos/{owner}/{repo} endpoint. The problem here is that this allows us to edit a grand total of 34 different properties for a repository. In similar commands, we have a flag for each property, though I'm not sure if that wouldn't be a little much here. Should I go for that, or do we have a better idea here?

LordMZTE self-assigned this 2026-03-09 19:52:45 +01:00

Cyborus commented 2026-03-09 22:16:04 +01:00

Member

Copy link

I think many of the parameters to PATCH /repos/{owner}/{repo} can be in other commands, i.e. all the parameters enabling the units could be in a fj repo units command, and putting basic things like description, private & name in fj repo edit.

Alternatively, it could mimic git config, with fj repo config name <NAME> or fj repo config units.wiki.external_url <URL>

I think many of the parameters to PATCH /repos/{owner}/{repo} can be in other commands, i.e. all the parameters enabling the units could be in a fj repo units command, and putting basic things like description, private & name in fj repo edit. Alternatively, it could mimic git config, with fj repo config name \<NAME\> or fj repo config units.wiki.external_url \<URL\>

Cyborus added the Kind/Feature label 2026-03-09 22:16:10 +01:00

Cyborus added this to the v0.5.0 milestone 2026-03-09 22:16:13 +01:00

xiaoshihou commented 2026-03-09 22:36:36 +01:00

Author

Copy link

These are the flags available in glab repo update

text
FLAGS  

    --archive Whether the project should be archived.
    --defaultBranch New default branch for the project.
    -d --description New description for the project.

I think the rest are available via glab api.

Alternatively, it could be an interactive tui (choose field, input, confirm loop).

Just my thoughts.

These are the flags available in glab repo update FLAGS --archive Whether the project should be archived. --defaultBranch New default branch for the project. -d --description New description for the project. I think the rest are available via glab api. Alternatively, it could be an interactive tui (choose field, input, confirm loop). Just my thoughts.

LordMZTE referenced this issue from a pull request that will close it, 2026-03-10 11:53:16 +01:00 repo edit & repo units commands #349

Cyborus closed this issue 2026-04-09 16:08:38 +02:00

Sign in to join this conversation.

No Branch/Tag specified

BranchesTags

main

renovate/lock-file-maintenance

renovate/serde-saphyr-0.x

docs/contributing

no-port-in-refspec

login/v16.next.forgejo.org

crates-io-publish

0.5.x

compile-time-fluent

0.4.x

localization-alias-demo

api_url_field

v0.5.0

v0.4.1

v0.4.0

v0.3.0

v0.2.0

v0.1.1

v0.1.0

v0.0.4

v0.0.3

v0.0.2

v0.0.1

Labels

Clear labels[ Kind/Breaking Breaking change that won't be backward compatible

](#)[ Kind/Bug Something is not working

](#)[ Kind/Design Discussion about UI/UX design

](#)[ Kind/Documentation Documentation changes

](#)[ Kind/Enhancement Improve existing functionality

](#)[ Kind/Feature New functionality

](#)[ Kind/Security This is security issue

](#)[ Kind/Testing Issue or pull request related to testing

](#)[ Kind/Upstream This is an issue with upstream software (Forgejo) that is probably not our fault

](#)

[ Priority

Critical The priority is critical

](#)[ Priority

High The priority is high

](#)[ Priority

Low The priority is low

](#)[ Priority

Medium The priority is medium

](#)

[ Reviewed

Confirmed Issue has been confirmed

](#)[ Reviewed

Duplicate This issue or pull request already exists

](#)[ Reviewed

Invalid Invalid issue

](#)[ Reviewed

Won't Fix This issue won't be fixed

](#)

[ Status

Abandoned Somebody has started to work on this but abandoned work

](#)[ Status

Blocked Something is blocking this issue or pull request

](#)[ Status

Need More Info Feedback is required to reproduce issue or to continue work

](#)

[ Suspicious

](#)

No labels Kind/Breaking Kind/Bug Kind/Design Kind/Documentation Kind/Enhancement Kind/Feature Kind/Security Kind/Testing Kind/Upstream [ Priority

Critical ](/forgejo-contrib/forgejo-cli/issues?labels=173012) [ Priority

High ](/forgejo-contrib/forgejo-cli/issues?labels=173013) [ Priority

Low ](/forgejo-contrib/forgejo-cli/issues?labels=173015) [ Priority

Medium ](/forgejo-contrib/forgejo-cli/issues?labels=173014) [ Reviewed

Confirmed ](/forgejo-contrib/forgejo-cli/issues?labels=173007) [ Reviewed

Duplicate ](/forgejo-contrib/forgejo-cli/issues?labels=173005) [ Reviewed

Invalid ](/forgejo-contrib/forgejo-cli/issues?labels=173006) [ Reviewed

Won't Fix ](/forgejo-contrib/forgejo-cli/issues?labels=173008) [ Status

Abandoned ](/forgejo-contrib/forgejo-cli/issues?labels=173011) [ Status

Blocked ](/forgejo-contrib/forgejo-cli/issues?labels=173010) [ Status

Need More Info ](/forgejo-contrib/forgejo-cli/issues?labels=173009) Suspicious

Milestone

Clear milestone

No items

No milestone v0.5.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

LordMZTE

3 participants

Notifications Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

forgejo-contrib/forgejo-cli#345

WritePreview

Loading…

Add table

| Rows | | | Columns | |

CancelOK

Add a link

Url Description Hint: With a URL in your clipboard, you can paste directly into the editor to create a link.

CancelOK

CancelSave

Reference in a new issue

Repository

forgejo-contrib/forgejo-cli

Title

Body

Create issue

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

No Yes