From 2a19baff7b2c861a84660bb4f40c56209f4ee387 Mon Sep 17 00:00:00 2001
From: lukaszcl <120112546+lukaszcl@users.noreply.github.com>
Date: Wed, 4 Sep 2024 14:22:54 +0200
Subject: [PATCH] more docs

---
 .github/README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.github/README.md b/.github/README.md
index 314dec13da6..041100a2842 100644
--- a/.github/README.md
+++ b/.github/README.md
@@ -37,6 +37,8 @@ Triggered manually by QA for specific testing needs.
 
 E2E tests utilize TOML files to define their parameters. Each test is equipped with a default TOML config, which can be overridden by specifying an alternative TOML config. This allows for running tests with varied parameters, such as on a non-default blockchain network. For tests executed on GitHub CI, both the default configs and any override configs must reside within the git repository. The `test_config_override_path` workflow input is used to provide a path to an override config.
 
+Config overrides should be stored in `testconfig/*/overrides/*.toml`. Placing files here will not trigger a rebuild of the test runner image.
+
 **Important Note:** The use of `base64Config` input is deprecated in favor of `test_config_override_path`. For more details, refer to [the decision log](https://smartcontract-it.atlassian.net/wiki/spaces/TT/pages/927596563/Storing+All+Test+Configs+In+Git).
 
 ## Test Secrets