From 7cd4a419fd741a27491973935978cea446ea9376 Mon Sep 17 00:00:00 2001 From: DongHyeonka Date: Sat, 7 Nov 2026 17:37:52 +0900 Subject: [PATCH] feat(gitea): enable Actions at the server level The template repositories cannot run CI: [actions] ENABLED=false and repo.actions in DISABLED_REPO_UNITS make Gitea ignore has_actions=true on the repository API (200 response, value unchanged). Turn on [actions] and drop only repo.actions from DISABLED_REPO_UNITS. Packages stay disabled (packages.ENABLED=false, repo.packages kept). Repositories created while the unit was disabled have no Actions unit row, so every existing repository keeps has_actions=false until its owner enables it. The values file is shared by the baseline and OIDC build roots, so both renders change the same way. Risk: new repositories get repo.actions by default (Gitea default DEFAULT_REPO_UNITS). They run nothing without a runner in scope. Gitea itself needs no new egress; runners connect inbound over the existing Host Nginx -> Traefik HTTPS path. Refs: Gitea 1.27 config cheat sheet [actions], [repository] --- services/gitea/profiles/oidc/values/baseline.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/services/gitea/profiles/oidc/values/baseline.yaml b/services/gitea/profiles/oidc/values/baseline.yaml index 1a516ff..86db703 100644 --- a/services/gitea/profiles/oidc/values/baseline.yaml +++ b/services/gitea/profiles/oidc/values/baseline.yaml @@ -95,12 +95,14 @@ gitea: queue: TYPE: level + # Actions is on at the server level. Repositories created while the unit + # was disabled keep has_actions=false until an owner turns it on. actions: - ENABLED: false + ENABLED: true packages: ENABLED: false repository: - DISABLED_REPO_UNITS: "repo.packages,repo.actions" + DISABLED_REPO_UNITS: "repo.packages" additionalConfigFromEnvs: - name: GITEA__DATABASE__USER