diff options
| author | MarcoFalke <[email protected]> | 2020-10-04 09:02:29 +0200 |
|---|---|---|
| committer | MarcoFalke <[email protected]> | 2020-10-04 09:05:59 +0200 |
| commit | 06314fbb5521bf9666e1523f09bfbf78aa976b1b (patch) | |
| tree | e3ae3001f10ec30b3179bdbd9a4bf593865bd0fd /src/script/script.cpp | |
| parent | Merge #19956: rpc: Improve invalid vout value rpc error message (diff) | |
| parent | lint: Use TRAVIS_BRANCH in lint-git-commit-check.sh (diff) | |
| download | discoin-06314fbb5521bf9666e1523f09bfbf78aa976b1b.tar.xz discoin-06314fbb5521bf9666e1523f09bfbf78aa976b1b.zip | |
Merge #20071: ci, lint: Remove usage of TRAVIS_COMMIT_RANGE
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
Diffstat (limited to 'src/script/script.cpp')
0 files changed, 0 insertions, 0 deletions