Very cool, we're doing similar except we let agents open PRs as well + we track release metadata and agentic sessions via our ReARM system + we've recently launched an option for agents to track helm-based deployments via ReARM - https://docs.rearmhq.com/workflows/devops.html

▲

rsgm 6 hours ago | parent [-]

I didn't mention this part, but while writing this I realized I could easily add a skill to hit the Forgejo PR API. There's no forgejo CLI like there is with GitHub sadly.

▲

kenosha 27 minutes ago | parent | next [-]

I just use the tea CLI. There is pretty good compatibility between tea and forgejo. The only place I’ve found it to be incomplete is forgejo’s actions api was missing some endpoints.

▲

t0mas88 4 hours ago | parent | prev | next [-]

There is, but it's limited. For example Forgejo does not expose CI build logs via the API so it's hard to make Claude auto-fix a build issue.

I still need to find the time to get into the Forgejo code and add that endpoint.

▲

cosnenc 5 hours ago | parent | prev | next [-]

There is: https://forgejo.org/docs/latest/admin/command-line/

	▲	mfenniak 5 hours ago \| parent [-]
		That's not an API tool. It performs direct database access for administrative functions on the Forgejo server. But there is a different tool that is an API accessing CLI: https://codeberg.org/forgejo-contrib/forgejo-cli

▲

bityard 5 hours ago | parent | prev [-]

That seems like a problem an LLM could solve. ;) (Assuming Forgejo has a reasonable REST/whatever API.)