dab156b452
This is in preparation of the migration of the v*.next.forgejo.org instances currently managed at https://code.forgejo.org/infrastructure/k8s The key difference is that the former system relies on ad-hoc scripts and creates one k8s cluster for each instance, sharing nothing between them. The newer k8s cluster is used for all and requires significantly less ad-hoc tooling. See also: * https://code.forgejo.org/infrastructure/next-digest * https://code.forgejo.org/infrastructure/k8s-cluster/src/branch/main/k8s.md#updating-v-next-forgejo-org |
||
|---|---|---|
| .. | ||
| backport.yml | ||
| build-release-integration.yml | ||
| build-release.yml | ||
| cascade-setup-end-to-end.yml | ||
| forgejo-integration-cleanup.yml | ||
| mirror.yml | ||
| publish-release.yml | ||
| release-notes-assistant-milestones.yml | ||
| release-notes-assistant.yml | ||
| renovate.yml | ||
| testing.yml | ||