Skip to content

INTPYTHON-631 Fix Typos in new evergreen patch instructions #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 2, 2025
Merged

INTPYTHON-631 Fix Typos in new evergreen patch instructions #73

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9d7b924
Fix typo in example in section: Running a patch build of a given PR
caseyclements May 28, 2025
08f1bde
Add example and fix 2nd typo (missing description)
caseyclements May 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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-pipelin-testing --param REPO_ORG="<my-org>" --param REPO_BRANCH="<my-branch>" -y "<my-message>"
evergreen patch -p ai-ml-pipeline-testing --param REPO_ORG="<my-org>" --param REPO_BRANCH="<my-branch>" -y -d "<my-message>"
```

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."
```