From c55a097100b8ddb02766999159c4ba64903be309 Mon Sep 17 00:00:00 2001 From: Ian Suvak Date: Fri, 23 Aug 2024 13:58:12 -0400 Subject: [PATCH] Update README.md Co-authored-by: bernard-avalabs <53795885+bernard-avalabs@users.noreply.github.com> Signed-off-by: Ian Suvak --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index eb9ce58b..7fc506c6 100644 --- a/README.md +++ b/README.md @@ -29,7 +29,7 @@ The most complicated example case that can arise above is that a feature depends ### Remote E2E testing through GitHub Actions 1. If an `avalanchego` commit referencing this change in its `go.mod` file doesn't exist yet then it needs to be added. -2. In `subnet-evm` add a commit that references the `avalanchego` commit from above in both its `go.mod` file as well as `scripts/versions.sh` file. +2. Add a commit in `subnet-evm` that references the `avalanchego` commit from above in both its `go.mod` file as well as its `scripts/versions.sh` file. 3. Create a new commit in this repository referencing `avalanchego` and `subnet-evm` directly and `coreth` indirectly as well as update references in the `scripts/version.sh` file for both `AVALANCHEGO_VERSION` and `SUBNET_EVM_VERSION`. If all of the commits mentioned above are published to GitHub branches, this will enable running of E2E tests through the CI.