forgejo-contrib-forgejo-cli-issues-545.md
Watch20
Star402
Fork
You've already forked forgejo-cli
CodeIssues 44Pull requests 8Releases 11Packages 2WikiActivity
Open
opened 2026-07-03 05:17:05 +02:00 by steffo · 1 comment
steffo commented 2026-07-03 05:17:05 +02:00
Copy link
I think it would be useful if fj had a way to interact with the topics of a repository, either as a standalone command fj repo topics (?) or as a --topics option of fj repo edit.
I believe this interaction can be done via the PUT /repos/{owner}/{repo}/topics method of the Forgejo API.
I'm making a script to automatically add topics to my repositories depending on what files are detected in them.
For example, if there's a Cargo.toml file in the repository root, automatically add [rust] to the topics.
fj had a way to interact with the topics of a repository, either as a standalone command fj repo topics (?) or as a --topics option of fj repo edit. I believe this interaction can be done via the PUT /repos/{owner}/{repo}/topics method of the Forgejo API. ### Motivation I'm making a script to automatically add topics to my repositories depending on what files are detected in them. For example, if there's a Cargo.toml file in the repository root, automatically add [rust] to the topics. ### Code of Conduct - [x] I agree to act in accordance with the CoC & AI Agreement. - [x] This issue was not generated by an LLM, even in part.👍 1
steffo added the Kind/Feature label 2026-07-03 05:17:05 +02:00
steffo referenced this issue 2026-07-03 05:40:16 +02:00 Add a way to set repository avatars #546
Fluffinity commented 2026-07-03 12:31:32 +02:00
Contributor
Copy link
One thing I currently wonder is what the most likely workflow would be. So are you most likely to set your topics once and forget and if you add/remove topics, would it be typically only one topic at a time? Depending on these things either fj repo topics or gj repo edit --topics would be a better fit. I would only really set the topics once and be done with it, but perspectives may differ.
One thing I currently wonder is what the most likely workflow would be. So are you most likely to set your topics once and forget and if you add/remove topics, would it be typically only one topic at a time? Depending on these things either fj repo topics or gj repo edit --topics would be a better fit. I would only really set the topics once and be done with it, but perspectives may differ.
Sign in to join this conversation.
No Branch/Tag specified
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
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
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#545
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