build(deps-dev): bump cz-customizable from 6.3.0 to 7.0.0

[dependabot]

Bumps cz-customizable from 6.3.0 to 7.0.0.

Release notes

Sourced from cz-customizable's releases.

v6.9.1

6.9.1 (2022-07-15)

Bug Fixes

• shell special characters escaping (#108) (d9fd78a), closes #107

v6.9.0

6.9.0 (2022-07-02)

Features

• ability to run via npx and global cz-cust alias (#191) (7c4df15)

v6.8.0

6.8.0 (2022-07-02)

Features

• remove several deps improve testing code (#188) (f5ea0eb)

v6.7.0

6.7.0 (2022-06-28)

Features

• Allow to skip scope question (#152) (c02c734)

v6.6.0

6.6.0 (2022-06-28)

Features

• semantic npm i (b947763)

v6.5.0

6.5.0 (2022-06-28)

Features

• semantic npm i (d477b4e)

v6.4.0

6.4.0 (2022-06-28)

... (truncated)

Commits

• 8a3ef9f fix: add option usePreparedCommit default false (#196)
• 9b82ca8 fix: downgrade inquirer for customScope bug fix (#202)
• 5539af6 docs: update readme
• d9fd78a fix: shell special characters escaping (#108)
• 0ad552e test: add unit tests (#198)
• 9a3f73d chore: update minimist sec (#197)
• 03efbf0 chore: update many deps
• 3a0fb50 build(deps): bump ajv from 6.10.0 to 6.12.6 (#189)
• 8b9359c build(deps): bump ansi-regex from 3.0.0 to 3.0.1 (#193)
• 21e4246 docs: comment out skip question (#192)
• 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)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
dgiot-doc	✅ Ready (Inspect)	Visit Preview	Nov 2, 2022 at 7:02AM (UTC)

[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: 1

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

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.