Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: upgrade to Husky 7 #6304

Merged
merged 1 commit into from
Jan 10, 2022
Merged

chore: upgrade to Husky 7 #6304

merged 1 commit into from
Jan 10, 2022

Conversation

nschonni
Copy link
Contributor

Motivation

Newer husky changed the need moved the post-install to prepare script, so a few other packages could now be dropped

Have you read the Contributing Guidelines on pull requests?

(Write your answer here.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)

Related PRs

(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

- Upgrade to Husky 7
- Update install hook to "prepare"
- Remove parallel/CI packages
@facebook-github-bot
Copy link
Contributor

Hi @nschonni!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

@netlify
Copy link

netlify bot commented Jan 10, 2022

✔️ [V2]
Built without sensitive environment variables

🔨 Explore the source changes: 12f4ee1

🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/61dbdeee5f62a400070303a7

😎 Browse the preview: https://deploy-preview-6304--docusaurus-2.netlify.app

@github-actions
Copy link

⚡️ Lighthouse report for the changes in this PR:

Category Score
🟠 Performance 68
🟢 Accessibility 98
🟢 Best practices 100
🟢 SEO 100
🟢 PWA 95

Lighthouse ran on https://deploy-preview-6304--docusaurus-2.netlify.app/

@Josh-Cena Josh-Cena added the pr: maintenance This PR does not produce any behavior differences to end users when upgrading. label Jan 10, 2022
Copy link
Collaborator

@Josh-Cena Josh-Cena left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! As soon as the CLA check passes we can merge.

@nschonni
Copy link
Contributor Author

I signed it, so the bot is probably just sneaker-netting it somewhere

@Josh-Cena
Copy link
Collaborator

Josh-Cena commented Jan 10, 2022

I have a question: last time I investigated, it seems prepare is executed at the end of virtually every script. However, it seems we currently don't install husky during CI (hence is-ci || husky install). Is there any reason for removing that check?

Husky is now installed for CI. Compare:
https://github.com/facebook/docusaurus/runs/4758213712?check_suite_focus=true
https://github.com/facebook/docusaurus/runs/4757919573?check_suite_focus=true

I don't think it's very problematic though, since AFAIK we never commit during CI

@Josh-Cena
Copy link
Collaborator

Yeah, it can take a while for the CLA check to come through, no worries😉

@nschonni
Copy link
Contributor Author

Looks like they do still talk about it in https://typicode.github.io/husky/#/?id=disable-husky-in-cidocker. I thought it fully wasn't needed because they had dropped the old env variables to skip the install.
I can add it back if you want

@Josh-Cena
Copy link
Collaborator

I have no idea why we had that check in the first place since we don't git commit in CI, but I'm fine with removing it since it probably only saves a few seconds of installation. Any value you can see in not installing for CI?

@nschonni
Copy link
Contributor Author

Not really. I could see it maybe tripping up on repos that use semantic-relaese plugins and commitlint, but I don't think it should matter here

@Josh-Cena
Copy link
Collaborator

Sure, let's go with this way👍 The check was added when we did the v4 -> v5 bump.

@facebook-github-bot facebook-github-bot added the CLA Signed Signed Facebook CLA label Jan 10, 2022
@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@Josh-Cena
Copy link
Collaborator

Okay, let's go!

@Josh-Cena Josh-Cena merged commit 291a2d6 into facebook:main Jan 10, 2022
@nschonni nschonni deleted the husky-7 branch January 10, 2022 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed Signed Facebook CLA pr: maintenance This PR does not produce any behavior differences to end users when upgrading.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants