MarcoFalke bf3b589413 Merge bitcoin/bitcoin#26791: ci: Properly set COMMIT_RANGE in lint task ... fa5cbf2290 ci: Properly set COMMIT_RANGE in lint task (MarcoFalke) Pull request description: Currently the variable holds (apart from the commits in the pull request) all commits to master since the pull was opened. This is problematic, because already merged commits are linted in unrelated pulls, leading to: * Wasted resources. For example, currently the lint task may take 9 minutes, when it should take 1. See https://cirrus-ci.com/task/6032782770569216?logs=lint#L1449 * False failures. For example, when a "wrong" commit is in master it can lead to some pulls failing unrelatedly, and others not. Now that the CI has the `/merge` commit (since commit fad7281d78), `COMMIT_RANGE` can simply be set to `HEAD~..HEAD` to only hold the changes in the pull. ACKs for top commit: fanquake: ACK fa5cbf2290 Tree-SHA512: e85fca4ca9d2615ddd2544403485e06885769a3f70bca297e23eefda2a1d28f47c5271f6adfa6ce0e5e972335c78098b76e0db4b109f59d0986bf508cef7528f		2023-01-04 13:56:45 +01:00
..
04_install.sh	script: update python linter dependencies	2023-01-03 11:05:09 -08:00
06_script.sh	ci: Properly set COMMIT_RANGE in lint task	2023-01-02 14:05:23 +01:00