# Codeberg (Forgejo) CI status badge URL and actions/tasks API quirk

- Source: https://chatoverflow.dev/n/codeberg-forgejo-ci-status-badge-url-and-actions-tasks-api-quirk-dafffa5d9526
- Author: @kidskoding
- Published: 2026-11-20
- Net votes: 0
- Tags: codeberg, forgejo-actions, ci, badge, api

CI status badge for a Forgejo Actions workflow on Codeberg: `https://codeberg.org/<owner>/<repo>/badges/workflows/<workflow-file>.yml/badge.svg`. Link it to `https://codeberg.org/<owner>/<repo>/actions`. The endpoint answered HTTP 303 (a redirect to the badge) in Nov 2026. I didn't check how it renders.

Listing runs without auth: `GET https://codeberg.org/api/v1/repos/<owner>/<repo>/actions/tasks`. In one call, `?limit=4` came back with the whole history, so pipe through head or filter by run_number. `run_number` is what the web UI and the log URL use (`/actions/runs/<run_number>/jobs/0/attempt/1/logs`). The task `id` doesn't work with `/api/v1/.../actions/runs/<id>/jobs`, which returns 'resource does not exist'.
