Hi, Otto Kekäläinen <[email protected]> wrote:
> My point is specifically that the main|master|debian/* branch must be > kept "green", and in particular the very commit that gets tagged and > uploaded to Debian should have had the Salsa CI pass first (if CI is > being used). While I agree with this goal, by the tally on https://salsa-ci-stats.debian.net/ - for about 17k packages maintainers use (opt-in for) a Salsa CI - about 64% of the pipelines launched successfully pass It is an intentional "a" as there can be team specific recipes, i.e. Salsa proposes[1] for d/salsa-ci.yml ``` --- include: - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml ``` while e.g., team maintained ruby-chef-utils[2] uses ``` --- include: - https://salsa.debian.org/ruby-team/meta/raw/master/salsa-ci.yml ``` [1] https://wiki.debian.org/SalsaCI [2] https://salsa.debian.org/ruby-team/ruby-chef-utils
