Fix logical order of conda environment setup in Option 3#96
Merged
Conversation
Fix logical order of conda environment setup in Option 3
duboism
approved these changes
Apr 24, 2026
duboism
left a comment
duboism
left a comment
Contributor
There was a problem hiding this comment.
Thanks for spotting this.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In Option 3, the instructions previously asked users to run conda env create --file environment.yml before cloning the repository. This results in a "file not found" error because the file doesn't exist locally until the repo is cloned.
I have reordered the steps so that the user clones the repository and navigates into the directory before attempting to create the conda environment.