de5d85504d
Gitea runs .github/workflows alongside .gitea/workflows, so pushing this fork started firing BloopAI's pipelines on our runner. Three of them trigger on push -- test.yml, remote-deploy-dev.yml and relay-deploy-dev.yml -- and the deploy pair aims at BloopAI's own infrastructure. They fail on missing secrets rather than doing anything, but a fork should not be attempting to deploy to the infrastructure of the project it forked from, and the noise buries our own build. The prod deploy and release workflows are workflow_dispatch or repository_dispatch only, so they were not firing, but they are equally meaningless here and go with the rest. .gitea/workflows/container.yml is now the only CI in this repo. Anything worth salvaging -- test.yml especially, once it is pointed at our own runner -- is recoverable from history.