Hi! > > Salsa CI is a great system for all aspiring Debian packagers to test > > their packages before requesting review from mentors > > > However, as there are still packages not using Salsa CI, I wonder is > > it straightforward enough for everyone? > > > > I think the best solution would be to make it opt-in rather than > opt-out? > > i think the barrier is likely to be "i didnt know you could do that?" > rather than "how do i use that?"
Salsa CI is and has always been opt-in. One needs to add a `debian/salsa-ci.yml` file to the Debian packaging repository for it to run: --- include: - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml AND additionally enable CI in the project settings in web ui or by running: salsa update_projects $NAMESPACE/$PROJECT --jobs yes --ci-config-path debian/salsa-ci.yml If it is running somewhere without a `debian/salsa-ci.yml` file it is probably because at some point people considered adding that salsa-ci.yml file too much work, and enabled Salsa CI via reference to `recipes/debian.yml@salsa-ci-team/pipeline` which is no longer recommended practice. I will clarify the README on this point and why skipping the salsa-ci.yml file is likely causing extra work for people in the long run. > > I am in the process of doing a round of updates to the README. All > > feedback on how to improve the documentation so it is easy to digest > > in particular for newcomers is welcome as replies to this email or as > > comments at > > https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/563. > > I added some comments, clearer docs are always worthwhile Thanks! I will update the draft soon.
