Specify pip3 in the file where it got blown away by a rebase #154
Conversation
This file contains 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
jmorrowomni
requested review from
dav3r,
felddy,
jsf9k and
mcdonnnj
as code owners
dav3r
approved these changes
Feb 10, 2023
jmorrowomni
added
the
improvement
jmorrowomni
force-pushed
the
improvement/update_pip3
branch
from
4ea88bf to
7aab074
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Specify pip3 in the file where it got blown away by a rebase
🗣 Description
Specify pip3 in the file where it got blown away by a rebase
💭 Motivation and context
PR #142 replaced all instances of pip with pip3. During a rebase
after merging PR #143, there was a conflict where a single instance of
this change was accidentally blown away and needs to be restored.
🧪 Testing
No additional testing required as all tests passed in #142.
✅ Pre-approval checklist