Thoughs on adding CI jobs on all the Python Team's repositories ?

Hi!

We've been talking in the Python Team about modifying our practices to run the Salsa Pipeline or some other standard CI pipeline on all the packages we have in the DPMT and PAPT.

I was wondering if there was any technical limitations on your side against that.

We'd make that change with git push -o ci.skip (or some other similar solution) to be sure not to overwhelm the runners when/if we decide to go that way. That way, only the next commit on the repos would trigger a CI run.

We currently have a total of 1948 repositories in the Python Team on Salsa.