MarcoFalke a53ef19d99 Merge #20071: ci, lint: Remove usage of TRAVIS_COMMIT_RANGE ... BACKPORT NOTICE There's some difference with original PR but that's not important because we do not actually use travis. The variable TRAVIS_BRANCH would be removed anyway in bitcoin#20697 - let's just skip it for simplicity -------------- a91ab86fae91d416d664d19d2f482a8d19c115a6 lint: Use TRAVIS_BRANCH in lint-git-commit-check.sh (Fabian Jahr) c11dc995c98e908dfd9cea64d4b34329b1dbb5c6 lint: Don't use TRAVIS_COMMIT_RANGE in whitespace linter (Fabian Jahr) 1b41ce8f5f3debae03ca60e4acada14680df9185 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: ACK a91ab86fae91d416d664d19d2f482a8d19c115a6. See test I tried in #20075. Tree-SHA512: 1378bdebd5d8787a83fbda5d9999cc9447209423e7f0218fe5eb240e6a32dc1b51d1cd53b4f8cd1f71574d935ac5e22e203dfe09cce17e9976a48416038e1263		2024-01-27 22:44:49 -06:00
..
04_install.sh	Merge #19348: test: Bump linter versions	2024-01-27 22:44:47 -06:00
05_before_script.sh	Merge #17829: scripted-diff: Bump copyright of files changed in 2019	2023-12-06 11:40:14 -06:00
06_script.sh	Merge #20071: ci, lint: Remove usage of TRAVIS_COMMIT_RANGE	2024-01-27 22:44:49 -06:00