Guard husky prepare so installs without husky don't fail#16
Open
melissa-barca wants to merge 1 commit into
Open
Guard husky prepare so installs without husky don't fail#16melissa-barca wants to merge 1 commit into
melissa-barca wants to merge 1 commit into
Conversation
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.
Both the root and
ai-provider-bridgepreparescripts runhuskyon everynpm install. When ai-lib is installed as a submodule workspace in a context where husky isn't on PATH (CI, production installs),sh -c huskyexits 127 and fails the whole install. Guarding each with|| truemakespreparea no-op in those cases while still setting up hooks in a normal dev clone.Surfaced installing the ai-lib submodule in Positron CI (posit-dev/positron#14928): the extension's own ai-config build succeeded, then the install failed on
sh -c husky.