Add get_workflow_log tool #212
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#212
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?
For agents to investigate workflow run issues, a
get_workflow_logtool would be required. This shall retrieve the detailed log of a workflow run./triage
🤖 Automated triage
Summary: A contributor requests a new
get_workflow_logtool so that AI agents can fetch and inspect CI workflow run logs without resorting to HTML scraping or host-level access. The motivation (debugging failing runs) is clear. Notably, open PR #126 already implements closely related tooling (get_workflow_run_job_logs), suggesting the feature is in progress and this issue may be satisfied once that PR lands.Labels applied:
Kind/Feature