Issues - Phil/forgejo-mcp - Philflow Forgejo

Phil/forgejo-mcp

Search syntax

`assignee:<username>`	Filter by assigned user
`author:<username>`	Filter by the author
`is:all`	All
`is:closed`	Closed
`is:open`	Open
`mentions:<username>`	Filter by mentioned user
`modified:[>\|<]<date>`	Filter by last modified date
`review:<username>`	Filter by user who reviewed
`sort:<by>:[asc\|desc]`	Sort by: `created\|comments\|updated\|deadline`

New issue

Job logs are unreachable: get_job_logs 404s and its hint loops

#26 opened 2026-09-20 08:47:45 +00:00 by Phil 0 / 3

get_run_logs / get_job_logs always 404 on private repos

#25 opened 2026-09-19 14:14:57 +00:00 by Phil

Merge tool still claims master runs the full prod E2E by default

#22 opened 2026-09-18 05:57:25 +00:00 by Phil

add_issue_labels should accept label names, not only numeric IDs

#20 opened 2026-09-12 13:27:03 +00:00 by Phil

Fix failing TestDispatchWorkflowFn_LegacyFallbackOn204 on main

#17 opened 2026-09-03 13:54:52 +00:00 by Phil

feat(actions): wire log/artifact tools to v16 token REST API + add run-cancel tool

#14 opened 2026-07-10 13:57:21 +00:00 by Phil 0 / 5

Release pipeline: fork can't cut releases on forgejo.philflow.me (release.yml targets codeberg, no runner)

#11 opened 2026-06-17 09:20:24 +00:00 by Phil

get_run_logs/get_job_logs: 404 on Forgejo v14 — token auth rejected by web log route (needs artifact path or v16 REST API)

#9 opened 2026-06-17 09:07:50 +00:00 by Phil

dispatch_workflow: response-decode error returned after the workflow already fired → false-negative re-dispatch risk

#7 opened 2026-06-17 09:07:31 +00:00 by Phil