Earl Warren dab156b452 chore(ci): notify the k8s cluster about experimental releases ... 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		2024-10-30 19:44:55 +01:00
..
issue_template	Update security option in issue template	2024-10-14 18:55:32 +00:00
testdata/build-release	forgejo-cli is now a symlink and cannot be used for sanity checks	2024-10-17 06:59:05 +02:00
workflows	chore(ci): notify the k8s cluster about experimental releases	2024-10-30 19:44:55 +01:00
workflows-composite	ci: merge e2e workflow into testing.yml	2024-10-04 15:14:28 +02:00
cascading-pr-end-to-end	chore(ci): optimize end-to-end runs	2024-08-08 17:53:12 +02:00
cascading-release-end-to-end	chore(ci): optimize end-to-end runs	2024-08-08 17:53:12 +02:00
pull_request_template.md	Replace Developer Guide links with the new Contributor Guide one for PR template and release workflows comments.	2024-08-26 14:29:10 +03:00