Hi! tldr; Are people on the team fine with not using recipes/debian.yml@salsa-ci-team/pipeline as the default setting in future and using debian/salsa-ci.yml instead?
context: I was looking at which of the Salsa CI jobs take longest and consume most resources and stumbled across https://salsa.debian.org/python-team/packages/graph-tool The build uses more memory than available on a Salsa CI runner, and it has never, and will never build. The reason it had CI running anyway was that in the CI/CD configuration it had `recipes/debian.yml@salsa-ci-team/pipeline`, which in turn was added in all Python projects in an effort to enable CI to all packages. I suggest a better practice would be to have as the CI/CD configuration simply `debian/salsa-ci.yml` instead, so that the pipeline runs only on Debian branches and starts running only after a human added it there with intention and presumably that it actually passed initially when CI was introduced. I did this change now on the graph-tool project and also posted https://salsa.debian.org/python-team/packages/graph-tool/-/merge_requests/1 to have the state of Salsa CI in the project documented. - Otto
