Charles Plessy <ple...@debian.org> writes: > I have prepared a stub for a "Gateway to NEW" on Salsa: > > https://salsa.debian.org/newgateway-team > > I added `Debian` as a team member. > > I am under the impression that forking repositories will not be necessary: if > we provide CI pipeline packages like the salsa-ci project, and smart ways to > turn them on and off, then people can run their tests in their own > repositories. I have some new r-cran-* packages to prepare next week; I will > use them as a proof of principle. Everybody is welcome to be faster than me > to > test the idea. > > I am not entirely sure on where to continue the discussion, but maybe we can > try to leverage Salsa as much as possible for that as well?
Thanks for starting this -- could you re-enable Issues for the Pipelines project? I suggest to use 'lrc' in the pipeline. I already do this for many packages, and I just add - https://salsa.debian.org/debian/licenserecon/raw/main/debian/licenserecon.yml to the debian/salsa-ci.yml file, see entire example file below. It will cause a CI failure on any debian/copyright mistakes. Yes, false positives happens, and it doesn't always handle Autotools projects with a lot of generated files with complex licenses well. /Simon include: - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml - https://salsa.debian.org/debian/licenserecon/raw/main/debian/licenserecon.yml variables: SALSA_CI_ENABLE_WRAP_AND_SORT: 'true' SALSA_CI_WRAP_AND_SORT_ARGS: '-asbkt' SALSA_CI_DISABLE_APTLY: 0 SALSA_CI_LINTIAN_FAIL_WARNING: '1' SALSA_CI_AUTOPKGTEST_ALLOWED_EXIT_STATUS: '0'
signature.asc
Description: PGP signature
