Point issue-core ArgoCD Application at Forgejo Git source
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 5s

ArgoCD was still tracking gitea.coulomb.social, which lags Forgejo after the
registry migration. Sync issue-core workload manifests from forgejo.coulomb.social
so backend ConfigMap updates land on CoulombCore.

Also allow forgejo.coulomb.social in railiance-tenants AppProject sourceRepos.
This commit is contained in:
tegwick 2026-07-08 15:19:32 +02:00
parent c3e1525821
commit 60447e8b0a
3 changed files with 3 additions and 2 deletions

View file

@ -11,7 +11,7 @@ metadata:
spec:
project: railiance-tenants
source:
repoURL: https://gitea.coulomb.social/coulomb/issue-core.git
repoURL: https://forgejo.coulomb.social/coulomb/issue-core.git
targetRevision: main
path: k8s/railiance
destination: