git/.github, branch v2.31.7

Merge branch 'tb/ci-run-cocci-with-18.04'

2021-02-11T00:48:07Z

The version of Ubuntu Linux used by default at GitHub Actions CI has been updated to one that lack coccinelle; until it gets fixed, work it around by sticking to the previous release (18.04). * tb/ci-run-cocci-with-18.04: .github/workflows/main.yml: run static-analysis on bionic

Merge branch 'ab/detox-gettext-tests'

2021-02-10T22:48:33Z

Get rid of "GETTEXT_POISON" support altogether, which may or may not be controversial. * ab/detox-gettext-tests: tests: remove uses of GIT_TEST_GETTEXT_POISON=false tests: remove support for GIT_TEST_GETTEXT_POISON ci: remove GETTEXT_POISON jobs

.github/workflows/main.yml: run static-analysis on bionic

2021-02-08T22:38:07Z

GitHub Actions is transitioning workflow steps that run on 'ubuntu-latest' from 18.04 to 20.04 [1]. This works fine in all steps except the static-analysis one, since Coccinelle isn't available on Ubuntu focal (it is only available in the universe suite). Until Coccinelle can be installed from 20.04's main suite, pin the static-analysis build to run on 18.04, where it can be installed by default. [1]: https://github.com/actions/virtual-environments/issues/1816 Reported-by: Junio C Hamano Signed-off-by: Taylor Blau Signed-off-by: Junio C Hamano

ci: do not cancel all jobs of a matrix if one fails

2021-01-28T06:09:42Z

The CI/PR GitHub Actions workflow uses the 'matrix' strategy for the "windows-test", "vs-test", "regular" and "dockerized" jobs. The default behaviour of GitHub Actions is to cancel all in-progress jobs in a matrix if one of the job of the matrix fails [1]. This is not ideal as a failure early in a job, like during installation of the build/test dependencies on a specific platform, leads to the cancellation of all other jobs in the matrix. Set the 'fail-fast' variable to 'false' for all four matrix jobs in the workflow. [1] https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast Signed-off-by: Philippe Blain Signed-off-by: Junio C Hamano

ci: remove GETTEXT_POISON jobs

2021-01-21T23:50:00Z

A subsequent commit will remove GETTEXT_POISON entirely, let's start by removing the CI jobs that enable the option. We cannot just remove the job because the CI is implicitly depending on the "poison" job being a sort of "default" job in the sense that it's the job that was otherwise run with the default compiler, no other GIT_TEST_* options etc. So let's keep it under the name "linux-gcc-default". This means we can remove the initial "make test" from the "linux-gcc" job (it does another one after setting a bunch of GIT_TEST_* variables). I'm not doing that because it would conflict with the in-flight 334afbc76fb (tests: mark tests relying on the current default for `init.defaultBranch`, 2020-11-18) (currently on the "seen" branch, so the SHA-1 will almost definitely change). It's going to use that "make test" again for different reasons, so let's preserve it for now. Signed-off-by: Ævar Arnfjörð Bjarmason Signed-off-by: Junio C Hamano

Merge branch 'da/vs-build-iconv-fix'

2020-12-14T18:21:38Z

Build update. * da/vs-build-iconv-fix: ci(vs-build): stop passing the iconv library location explicitly

ci(vs-build): stop passing the iconv library location explicitly

2020-12-04T20:03:15Z

Something changed in `vcpkg` (which we use in our Visual C++ build to provide the dependencies such as libcurl) and our `vs-build` job started failing in CI. The reason is that we had a work-around in place to help CMake find iconv, and this work-around is neither needed nor does it work anymore. For the full discussion with the vcpkg project, see this comment: https://github.com/microsoft/vcpkg/issues/14780#issuecomment-735368280 Signed-off-by: Dennis Ameling Signed-off-by: Johannes Schindelin Signed-off-by: Junio C Hamano

Merge branch 'js/ci-github-set-env'

2020-11-11T21:18:39Z

CI update. * js/ci-github-set-env: ci: avoid using the deprecated `set-env` construct

Merge branch 'cw/ci-ghwf-check-ws-errors'

2020-11-11T21:18:38Z

Dev support update. * cw/ci-ghwf-check-ws-errors: ci: make the whitespace checker more robust

ci: avoid using the deprecated `set-env` construct

2020-11-07T06:06:13Z

The `set-env` construct was deprecated as of the announcement in https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ Let's use the recommended alternative instead. Signed-off-by: Johannes Schindelin Signed-off-by: Junio C Hamano