From 9d7b9247f7da462826b7eaca1a3040267aa57db0 Mon Sep 17 00:00:00 2001 From: Casey Clements Date: Wed, 28 May 2025 13:31:08 -0400 Subject: [PATCH 1/2] Fix typo in example in section: Running a patch build of a given PR --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2f28ce6..37b02d9 100644 --- a/README.md +++ b/README.md @@ -175,5 +175,5 @@ as they often have to build for a more broad set of scenarios than the original Rather than making a new branch and modifying a `config.env` file, you can run a patch build as follows: ```bash -evergreen patch -p ai-ml-pipelin-testing --param REPO_ORG="" --param REPO_BRANCH="" -y "" +evergreen patch -p ai-ml-pipeline-testing --param REPO_ORG="" --param REPO_BRANCH="" -y "" ``` From 08f1bde31906b3349e2b057f1cd5064ba3200f79 Mon Sep 17 00:00:00 2001 From: Casey Clements Date: Wed, 28 May 2025 16:05:18 -0400 Subject: [PATCH 2/2] Add example and fix 2nd typo (missing description) --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 37b02d9..e308be2 100644 --- a/README.md +++ b/README.md @@ -175,5 +175,10 @@ as they often have to build for a more broad set of scenarios than the original Rather than making a new branch and modifying a `config.env` file, you can run a patch build as follows: ```bash -evergreen patch -p ai-ml-pipeline-testing --param REPO_ORG="" --param REPO_BRANCH="" -y "" +evergreen patch -p ai-ml-pipeline-testing --param REPO_ORG="" --param REPO_BRANCH="" -y -d "" +``` + +For example +```bash +evergreen patch -p ai-ml-pipeline-testing --param REPO_ORG=caseyclements --param REPO_NAME="langchain-mongodb" --param REPO_BRANCH="INTPYTHON-629" -y -d "Increased retries to 4." ```