From 744d49501905144b4cef2c14efce37648130d078 Mon Sep 17 00:00:00 2001 From: Max Edwards Date: Wed, 17 Jun 2026 09:53:20 -0400 Subject: [PATCH] ci: updated docs to reflect removal of REPO_USE_WARP_RUNNERS flag --- ci/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ci/README.md b/ci/README.md index 0b6a34460ca..33c623dc2af 100644 --- a/ci/README.md +++ b/ci/README.md @@ -97,5 +97,5 @@ To configure the primary repository, follow these steps: When used in a fork the CI will run on GitHub's free hosted runners by default. In this case, GitHub's cache size limitations may cause caches to be frequently evicted and missed, but the workflows will run (slowly). -It is also possible to use your own WarpBuild Runners in your own fork with an appropriate patch to the `REPO_USE_WARP_RUNNERS` variable in ../.github/workflows/ci.yml +It is also possible to use your own WarpBuild Runners in your own fork by replacing the references to `bitcoin/bitcoin` in `../.github/workflows/ci.yml` with the name of your fork (e.g. `your-org/bitcoin`). NB that WarpBuild Runners only work at an organisation level, therefore in order to use your own WarpBuild Runners, *the fork must be within your own organisation*.