search

dgiot / iotStudio

dgiot平台行业应用扩展插件 dgiot for application plugin
https://dgiot-dashboard.vercel.app/
Mozilla Public License 2.0
283 stars 102 forks source link

chore(deps-dev): bump @commitlint/cli from 17.0.3 to 17.4.4 #658

Open dependabot[bot] opened 1 year ago

dependabot[bot] commented 1 year ago

Bumps @commitlint/cli from 17.0.3 to 17.4.4.

Release notes

Sourced from @​commitlint/cli's releases.

v17.4.4

17.4.4 (2023-02-17)

Bug Fixes

  • parse: allow setting fieldPattern in parserOpts (#3538) (ea23c65)

New Contributors

Full Changelog: https://github.com/conventional-changelog/commitlint/compare/v17.4.3...v17.4.4

v17.4.3

17.4.3 (2023-02-13)

Bug Fixes

Full Changelog: https://github.com/conventional-changelog/commitlint/compare/v17.4.2...v17.4.3

v17.4.2

17.4.2 (2023-01-12)

Bug Fixes

  • load: fixes a bug when a ts commitlint config is compiled twice (#3499) (dc2c899)

New Contributors

Full Changelog: https://github.com/conventional-changelog/commitlint/compare/v17.4.1...v17.4.2

v17.4.1

17.4.1 (2023-01-09)

Note: Version bump only for package @​commitlint/root

Full Changelog: https://github.com/conventional-changelog/commitlint/compare/v17.4.0...v17.4.1

v17.4.0

17.4.0 (2023-01-04)

Bug Fixes

... (truncated)

Changelog

Sourced from @​commitlint/cli's changelog.

17.4.4 (2023-02-17)

Note: Version bump only for package @​commitlint/cli

17.4.3 (2023-02-13)

Note: Version bump only for package @​commitlint/cli

17.4.2 (2023-01-12)

Note: Version bump only for package @​commitlint/cli

17.4.1 (2023-01-09)

Note: Version bump only for package @​commitlint/cli

17.4.0 (2023-01-04)

Bug Fixes

17.3.0 (2022-11-21)

Note: Version bump only for package @​commitlint/cli

17.2.0 (2022-10-31)

Features

17.1.2 (2022-08-29)

... (truncated)

Commits


Dependabot compatibility score

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)
pull-checklist[bot] commented 1 year ago

Example Check Group #2 (Click here to edit)

vercel[bot] commented 1 year ago

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

Name Status Preview Comments Updated
dgiot-dashboard ❌ Failed (Inspect) Feb 20, 2023 at 6:05AM (UTC)
pull-request-quantifier-deprecated[bot] commented 1 year ago

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](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

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](https://github.com/microsoft/PullRequestQuantifier/releases) - 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](./docs/prquantifier-yaml.md) 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? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.