How blender/gitea works
Project type and purpose
• This is an open-source “patch manager” CI/CD repository built around a fork of go-gitea/gitea.
• Its sole job is to maintain a set of custom patches (in patches/), automatically rebase them onto each new upstream release, build a patched Gitea OCI image, and push that image to your registry.
File structure
• .github/workflows/
• build.yml – the pipeline that builds & publishes the container image on code changes or PR merges.
• patch-release.yml – the pipeline that triggers on upstream gitea releases, creates a branch, applies all patches, and then triggers a build.
• patches/ – a numbered list of .patch files, each one a single change against upstream.
• README – describes the repo’s role, the ci branch, and how workflows stitch upstream → patches → build → push.
README for additional insights
• Confirms: ci branch is only for storing patches + workflows.
• Workflows create feature branches per upstream tag, apply the entire patch set, then build & push an OCI image.