docs: prepare script instead of postinstall #890
Merged
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
infotexture
added a commit
to dita-ot/docs
that referenced
this pull request
Mar 2, 2021
https://typicode.github.io/husky/#/?id=migrate-from-v4-to-v5 Additional changes: - Use prepare script instead of postinstall: typicode/husky#890 - Remove old package.json > husky field - Add `lint-staged` to package scripts & prefix `pre-commit` with npx typicode/husky#866 (comment) Signed-off-by: Roger Sheen <roger@infotexture.net>
infotexture
added a commit
to dita-ot/website
that referenced
this pull request
Mar 4, 2021
https://typicode.github.io/husky/#/?id=migrate-from-v4-to-v5 Additional changes: - Use prepare script instead of postinstall: typicode/husky#890 - Remove old package.json > husky field - Add `lint-staged` to package scripts & prefix `pre-commit` with npx typicode/husky#866 (comment) Signed-off-by: Roger Sheen <roger@infotexture.net>
This was referenced Mar 6, 2021
This was referenced Mar 16, 2021
14 tasks
damingerdai
added a commit
to damingerdai/angular
that referenced
this pull request
Apr 5, 2021
With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation.
damingerdai
added a commit
to damingerdai/angular
that referenced
this pull request
Apr 5, 2021
With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation.
damingerdai
added a commit
to damingerdai/components
that referenced
this pull request
Apr 6, 2021
With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation.
atscott
pushed a commit
to angular/angular
that referenced
this pull request
Apr 6, 2021
…1405) With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation. PR Close #41405
atscott
pushed a commit
to angular/angular
that referenced
this pull request
Apr 6, 2021
…1405) With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation. PR Close #41405
annieyw
pushed a commit
to angular/components
that referenced
this pull request
May 4, 2021
* build: update to husky@6 Upgrade husky from 5.2.0 to 6.0.0 * build: install husky in `prepare` script instead of `postinstall` With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation.
annieyw
pushed a commit
to angular/components
that referenced
this pull request
May 4, 2021
* build: update to husky@6 Upgrade husky from 5.2.0 to 6.0.0 * build: install husky in `prepare` script instead of `postinstall` With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation. (cherry picked from commit f19aca6)
trik
added a commit
to trik/ajf
that referenced
this pull request
Jun 9, 2021
* build: update to husky@6 Upgrade husky from 5.2.0 to 6.0.0 * build: install husky in `prepare` script instead of `postinstall` With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation.
trik
added a commit
to gnucoop/ajf
that referenced
this pull request
Jun 10, 2021
* build: update to husky@6 Upgrade husky from 5.2.0 to 6.0.0 * build: install husky in `prepare` script instead of `postinstall` With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation.
trik
added a commit
to gnucoop/gngt
that referenced
this pull request
Jun 15, 2021
* build: update to husky@6 Upgrade husky from 5.2.0 to 6.0.0 * build: install husky in `prepare` script instead of `postinstall` With typicode/husky#890, the recommended way to install husky is in the `prepare` script instead of the `postinstall`. This commit moves the husky installation to the `prepare` script to align with the new recommendation.
nikoladavitkovski
pushed a commit
to nikoladavitkovski/husky
that referenced
this pull request
Sep 2, 2022
Co-authored-by: Nathan Smith <nathan@sonspring.com>
1 task
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.
Many thanks to @nathansmith #884 for suggesting this improvement.