Add Windows compatibility for single-project install using install.sh
#259
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
added 2 commits
September 19, 2020 14:33
🐛 fix SC2076 quoted regex
derwent-m
force-pushed
the
feature/windows_compat
branch
from
605c913
to
e299a2b
Compare
|
@derwent-m , @harinee has made changes for moving away from specific HASH checks to verifying against published checksums. |
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.
Changes affecting install.sh (script used to install talisman to a single repo, not to be confused with global_install_scripts/install.bash ):
#198
Outstanding issues (existed before this PR):
install.shis broken on Windowsinstall.sh#260 you need to update the version number and SHA each time Talisman updates