feat/remove-issue-labels #96
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!96
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/remove-issue-labels"
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?
Closes #95
What
Adds a
remove_issue_labelsMCP tool, the missing counterpart to the existingadd_issue_labels.Why
Without it, an MCP agent can add labels but has no way to remove them — breaking simple label-lifecycle workflows (e.g. adding
in_progresswhen work starts, removing it when done).How
RemoveIssueLabelsToolNameRemoveIssueLabelsToolwith identical params toadd_issue_labelsRemoveIssueLabelsFn— iterates label IDs, callsforgejo.Client().DeleteIssueLabel()for each, returns updated issueRegisterTool()The change is ~40 lines in
operation/issue/issue.go. Tested live against a self-hosted Forgejo instance — add then remove confirmed working.