Fix update skills for local git clone installs#68
Merged
Conversation
When shipkit is installed from a local git clone, `pip install --upgrade` does nothing because pip sees the same version. The update skills now detect git clone installs and use `pip install --force-reinstall .` after pulling, which correctly reinstalls the updated code.
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
1 participant
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.
Summary
/updateand/update-shipkit) now detect local git clone installspip install --force-reinstall .aftergit pullfor git clones, sincepip install --upgradesees "same version" and skips/update-shipkitto check git clone firstTest plan