Woodpecker CI

Use this skill as an operating playbook, not as a substitute for checking the documentation for the installed major version. Prefer explicit SemVer image tags, verify the resolved configuration before starting services, and verify runtime health after every change.

Scope boundary: This skill configures and operates Woodpecker CI (the server, agents, workflows, and integrations). It does not install or administer Forgejo/Gitea itself, and it does not configure Forgejo Actions runners. When a task mentions Forgejo, treat it as the forge Woodpecker connects to unless forge administration is explicitly requested.

Operating loop

1. Identify the Woodpecker major version, forge, backend, deployment files, database, public URL, and whether the task is a setup, pipeline, or incident.
2. Read the matching reference below before changing configuration.
3. Render and lint configuration before starting the server or agent.
4. Make the smallest change at the layer that owns the problem: forge/OAuth, server, agent/backend, or repository workflow.
5. Verify the result at the next boundary: server health, agent connected state, repository webhook, pipeline scheduling, step logs, and external deployment endpoint.
6. Record the exact version and relevant environment variables without recording secret values.

Choose the entry point