Merge #20071: ci, lint: Remove usage of TRAVIS_COMMIT_RANGE
pull/764/heada91ab86fae
lint: Use TRAVIS_BRANCH in lint-git-commit-check.sh (Fabian Jahr)c11dc995c9
lint: Don't use TRAVIS_COMMIT_RANGE in whitespace linter (Fabian Jahr)1b41ce8f5f
lint: Don't use TRAVIS_COMMIT_RANGE for commit-script-check (Fabian Jahr) Pull request description: This is causing problems again, very similar to #19654. UPDATE: This now removes all remaining usages of TRAVIS_COMMIT_RANGE and instead uses TRAVIS_BRANCH for the range, including `lint-git-commit-check` where TRAVIS_COMMIT_RANGE had already been removed. For builds triggered by a pull request, TRAVIS_BRANCH is the name of the branch targeted by the pull request. In the linters there is still a fallback that assumes master as the target branch. ACKs for top commit: sipa: ACKa91ab86fae
. See test I tried in #20075. Tree-SHA512: 1378bdebd5d8787a83fbda5d9999cc9447209423e7f0218fe5eb240e6a32dc1b51d1cd53b4f8cd1f71574d935ac5e22e203dfe09cce17e9976a48416038e1263
commit
06314fbb55
Loading…
Reference in new issue