From: Michał Kępień Date: Fri, 31 Jan 2025 09:25:56 +0000 (+0100) Subject: Use default cloning depth for the Danger CI job X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=819bc583f19e652ec5241e90d0fa0d1b390c24ca;p=thirdparty%2Fbind9.git Use default cloning depth for the Danger CI job With shallow fetching working reliably in pygit2 1.17.0+, there is no longer any need for GitLab CI runners to clone the BIND 9 repository with a fixed depth of 1000 during every "danger" CI job as Hazard is now able to fetch remote refs with an arbitrary depth, controlled by the HAZARD_FETCH_DEPTH environment variable. The latter can be defined via GitLab project's CI settings and adjusted as needed over time, without the need to update .gitlab-ci.yml every time its value needs to be changed. (cherry picked from commit e39e7afc16fe1575afb907be76e55942925e1a3d) --- diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 69d10cc072c..4da726f83e8 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -341,11 +341,6 @@ coccinelle: danger: <<: *precheck_job - # Keep the GIT_DEPTH environment variable set to a "high number" before - # https://github.com/libgit2/libgit2/pull/6662 is addressed and integrated - # into pygit2. - variables: - GIT_DEPTH: 1000 needs: [] script: - pip install git+https://gitlab.isc.org/isc-projects/hazard.git