The Pipelines as Code documentation does not have explicit instructions for Gitea or its "successor" hard fork, Forgejo. However, based on several issues in this repo it is clear that some support/capabilities for these SCM providers are available.

See also:

• break gitea_test.go #2097
• Forgejo - User %s is not allowed to trigger CI via pull_request on this repo. #2103
• Add unit tests for pkg/provider/gitea/parse_payload.go #2146