merge-script 32368cd3e9 Merge bitcoin/bitcoin#33905: ci: Consistenly only cache on the default branch ...

fa411f938e ci: Consistenly only cache on the default branch (MarcoFalke)

Pull request description:

  Fixes https://github.com/bitcoin/bitcoin/issues/33685

  The general idea for caches is to only save them on pushes to the default branch, because the cache is limited in size and time that the only benefit of the cache can be to speed up pull requests against the default branch.

  Backport pull requests to older branches don't benefit from caches, because usually they will be running into a cache miss anyway. Also, they would cause the cache size to overflow and lead to cache misses down the line.

  So fix it by consistently applying cache saves only on the default branch.

  For reference, the same is already done for the composite action in this repo: 2444488f6a/.github/actions/save-caches/action.yml (L15)

ACKs for top commit:
  hebasto:
    ACK fa411f938e.
  willcl-ark:
    ACK fa411f938e

Tree-SHA512: 59d3de4201b596e5f7eb1915c4bd5ded80bcd4df217f8f5d62d92fa8977a77e2c4c8602b17755b33ff0dfa87f2896e7c1c8f4da8e6a77c111f2a42ec9cf78ffd

2025-11-20 17:17:16 +00:00

..

actions

ci: Rewrite Bash to check inputs to Python

2025-11-12 13:39:27 +01:00

ISSUE_TEMPLATE

doc: bump the template macOS version

2025-10-10 14:34:32 -04:00

workflows

Merge bitcoin/bitcoin#33905: ci: Consistenly only cache on the default branch

2025-11-20 17:17:16 +00:00

ci-test-each-commit-exec.py

ci: [refactor] Extract build_dir constant in ci-test-each-commit-exec.py

2025-11-08 09:47:08 +01:00

PULL_REQUEST_TEMPLATE.md

doc: Add redirect for GUI issues and pull requests

2020-06-08 10:06:02 -04:00