feat: add remove_issue_labels tool #95
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#95
Loading…
Reference in a new 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?
What's missing
The MCP server exposes
add_issue_labelsbut has no correspondingremove_issue_labelstool. There is no way to remove a label from an issue via MCP — you can only add them.The Forgejo API has
DELETE /repos/{owner}/{repo}/issues/{index}/labels/{id}but it's not wired up.Why it matters
Without this, an MCP agent that adds a label (e.g.
in_progress) during a workflow has no way to clean it up when the work is done. This breaks simple automation patterns that rely on label lifecycle.Proposed tool
remove_issue_labels— mirrorsadd_issue_labelsexactly:owner,repo,index,labels(comma-separated numeric IDs)DeleteIssueLabelonce per label (the API is per-ID, unlike the bulk add)I have an implementation ready on my fork if you'd like me to open a PR.
Ja sure, happy to get a pr!!
nice.
my first ever open source contribution too.