Skip to content

Commit 9d7b924

Browse files
committed
Fix typo in example in section: Running a patch build of a given PR
1 parent d7301f1 commit 9d7b924

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,5 +175,5 @@ as they often have to build for a more broad set of scenarios than the original
175175
Rather than making a new branch and modifying a `config.env` file, you can run a patch build as follows:
176176

177177
```bash
178-
evergreen patch -p ai-ml-pipelin-testing --param REPO_ORG="<my-org>" --param REPO_BRANCH="<my-branch>" -y "<my-message>"
178+
evergreen patch -p ai-ml-pipeline-testing --param REPO_ORG="<my-org>" --param REPO_BRANCH="<my-branch>" -y "<my-message>"
179179
```

0 commit comments

Comments
 (0)