.github/workflows/lab.yml (GitHub replica only): every push to a branch other than main runs inbuxa-k8s-lab's e2e against that chart commit, on Kubernetes 1.35, 1.36 and 1.37, amd64. main gets the lab's nightly run on both architectures.
The result goes back to the commit on Gitea as the status lab / e2e: pending when the run starts, then success, failure, or error if a newer push cancelled it. So a chart PR shows the lab's verdict, and the merge script waits for it like any other check. Only the two small status jobs hold GITEA_TOKEN (already a repo secret, write:repository); the lab itself runs without it. Branches come from this repo's own maintainers through the push mirror; a fork's PR doesn't reach GitHub, so no outside code runs with the secret.
Tested:this branch's own run: pending posted, three e2e jobs green, lab / e2e: success on the Gitea commit.
Before merging: this commit calls the lab's workflow at its branch feat/kl8-matrix. Once inbuxa/inbuxa-k8s-lab#32 merges, one more commit here switches it to @main and that run has to go green.
`.github/workflows/lab.yml` (GitHub replica only): every push to a branch other than main runs inbuxa-k8s-lab's e2e against **that chart commit**, on Kubernetes 1.35, 1.36 and 1.37, amd64. main gets the lab's nightly run on both architectures.
The result goes back to the commit on Gitea as the status **`lab / e2e`**: pending when the run starts, then success, failure, or error if a newer push cancelled it. So a chart PR shows the lab's verdict, and the merge script waits for it like any other check. Only the two small status jobs hold `GITEA_TOKEN` (already a repo secret, write:repository); the lab itself runs without it. Branches come from this repo's own maintainers through the push mirror; a fork's PR doesn't reach GitHub, so no outside code runs with the secret.
**Tested:** [this branch's own run](https://github.com/inbuxa/inbuxa-charts/actions/runs/44684881995): pending posted, three e2e jobs green, `lab / e2e: success` on the Gitea commit.
**Before merging:** this commit calls the lab's workflow at its branch `feat/kl8-matrix`. Once inbuxa/inbuxa-k8s-lab#32 merges, one more commit here switches it to `@main` and that run has to go green.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
.github/workflows/lab.yml(GitHub replica only): every push to a branch other than main runs inbuxa-k8s-lab's e2e against that chart commit, on Kubernetes 1.35, 1.36 and 1.37, amd64. main gets the lab's nightly run on both architectures.The result goes back to the commit on Gitea as the status
lab / e2e: pending when the run starts, then success, failure, or error if a newer push cancelled it. So a chart PR shows the lab's verdict, and the merge script waits for it like any other check. Only the two small status jobs holdGITEA_TOKEN(already a repo secret, write:repository); the lab itself runs without it. Branches come from this repo's own maintainers through the push mirror; a fork's PR doesn't reach GitHub, so no outside code runs with the secret.Tested: this branch's own run: pending posted, three e2e jobs green,
lab / e2e: successon the Gitea commit.Before merging: this commit calls the lab's workflow at its branch
feat/kl8-matrix. Once inbuxa/inbuxa-k8s-lab#32 merges, one more commit here switches it to@mainand that run has to go green.