fix(deps): bump husky from 7.0.4 to 8.0.3

[dependabot]

Bumps husky from 7.0.4 to 8.0.3.

Release notes

Sourced from husky's releases.

v8.0.3

• fix: add git not installed message #1208

v8.0.2

• docs: remove deprecated npm set-script

v8.0.1

• fix: use POSIX equality operator

v8.0.0

What's Changed

Feats

• feat: add husky - prefix to logged global error messages by @​joshbalfour in typicode/husky#1092
• feat: show PATH when command not found to improve debuggability
• feat: drop Node 12 support
• feat: skip install if $HUSKY=0

Fixes

• fix: hook script use /usr/bin/env sh instead of direct path of sh by @​skhaz in typicode/husky#1051
• fix: actually set 'husky_skip_init' as readonly in ./husky.sh by @​hyperupcall in typicode/husky#1104
• fix: force basename/dirname to treat $0 as an argument by @​mataha in typicode/husky#1132
• fix: remove git.io links by @​renbaoshuo in typicode/husky#1136

Docs

• docs: fix uninstall via npm by @​pddpd in typicode/husky#1033
• docs: add dog emoji as favicon by @​jamiehaywood in typicode/husky#1095
• docs: replace deprecated npx --no-install option with npx --no by @​sibiraj-s in typicode/husky#1070
• docs: add pnpm installation by @​MohamadKh75 in typicode/husky#1139

Chore

• chore: update workflows by @​tiziodcaio in typicode/husky#1125

Commits

• 3c0e08d 8.0.3
• 1ed3f9a fix: change message
• 500d450 fix: add git not installed error message (#1208)
• 2945907 chore(deps): bump minimatch from 3.0.4 to 3.1.2 (#1229)
• 9f6dac4 chore: remove stale bot
• f6c2c06 chore: update package-lock.json
• f862dc2 chore: update devDependencies
• 9efb720 8.0.2
• 573de60 docs: remove deprecated npm set-script
• 3db28d4 chore: increase daysUntilStale
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Dependabot tried to add @GregoireF and @NicolasV as reviewers to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/wr-projects/cz-changelog-wrprojects/pulls/190/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the wr-projects/cz-changelog-wrprojects repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}