forgejo-contrib-forgejo-cli-issues-435.md
Watch20
Star402
Fork
You've already forked forgejo-cli
CodeIssues 44Pull requests 8Releases 11Packages 2WikiActivity
Open
opened 2026-04-20 22:36:25 +02:00 by belak · 0 comments
belak commented 2026-04-20 22:36:25 +02:00
Copy link
I would like to propose milestones integration with the CLI. This would have a few separate parts, which could be implemented together or separately.
milestone sub-command (fj repo milestone), similar to the existing label command. It would have view, create, edit and delete subcommands (again, similar to label).fj issue search would gain a --milestones flag, similar to --labels.fj pr search would gain a --milestones flag, similar to --labels.fj issue create would gain a --milestone flag.fj issue edit <issue> milestoneNote: some endpoints seem to take milestone IDs, while others take milestone names. We should prefer names, as they're still unique and much more user friendly, even if that requires us to make an extra API request to resolve the name.
I would like the ability to programmatically perform crud operations against milestones on my forgejo instance. Additionally, searching by milestone to allow me to see what needs to be done for the next release.
milestone sub-command (fj repo milestone), similar to the existing label command. It would have view, create, edit and delete subcommands (again, similar to label). 2. The ability to search for issues referencing a specific milestone - fj issue search would gain a --milestones flag, similar to --labels. 3. The ability to search for PRs referencing a specific milestone - fj pr search would gain a --milestones flag, similar to --labels. 4. The ability to create issues referencing a specific milestone -fj issue create would gain a --milestone flag. 5. The ability to set the milestone for a given issue/pull request fj issue edit \<issue\> milestone Note: some endpoints seem to take milestone IDs, while others take milestone names. We should prefer names, as they're still unique and much more user friendly, even if that requires us to make an extra API request to resolve the name. ### Motivation I would like the ability to programmatically perform crud operations against milestones on my forgejo instance. Additionally, searching by milestone to allow me to see what needs to be done for the next release. ### 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
belak added the Kind/Feature label 2026-04-20 22:36:25 +02:00
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#435
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