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(deps-dev): bump lint-staged from 11.2.6 to 13.1.2 #656

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 14, 2023

Bumps lint-staged from 11.2.6 to 13.1.2.

Release notes

Sourced from lint-staged's releases.

v13.1.2

13.1.2 (2023-02-13)

Bug Fixes

  • disable stash by default when using diff option (#1259) (142c6f2)

v13.1.1

13.1.1 (2023-02-07)

Bug Fixes

  • allow re-enabling --stash when using the --diff option (99390c3)

v13.1.0

13.1.0 (2022-12-04)

Features

  • expose cli entrance from "lint-staged/bin" (#1237) (eabf1d2)

v13.0.4

13.0.4 (2022-11-25)

Bug Fixes

  • deps: update all dependencies (336f3b5)
  • deps: update all dependencies (ec995e5)

v13.0.3

13.0.3 (2022-06-24)

Bug Fixes

  • correctly handle git stash when using MSYS2 (#1178) (0d627a5)

v13.0.2

13.0.2 (2022-06-16)

Bug Fixes

  • use new --diff and --diff-filter options when checking task modifications (1a5a66a)

v13.0.1

... (truncated)

Commits
  • 142c6f2 fix: disable stash by default when using diff option (#1259)
  • f88b6b7 docs: fix broken links in readme (#1258)
  • 99390c3 fix: allow re-enabling --stash when using the --diff option
  • 421234c docs: add example to integrate with Next.js (#1256)
  • 8f63a0a docs: blog.johnnyreilly.com -> johnnyreilly.com (#1255)
  • 63cf9d8 docs: Update link to a blog post (#1246)
  • eabf1d2 feat: expose cli entrance from "lint-staged/bin" (#1237)
  • a987e6a docs: add note about multiple configs files to README
  • c4fb7b8 docs: add note about git hook TTY to README
  • e2bfce1 test: remove Windows snapshot workaround
  • Additional commits viewable in compare view

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)

Bumps [lint-staged](https://github.com/okonet/lint-staged) from 11.2.6 to 13.1.2.
- [Release notes](https://github.com/okonet/lint-staged/releases)
- [Commits](lint-staged/lint-staged@v11.2.6...v13.1.2)

---
updated-dependencies:
- dependency-name: lint-staged
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 14, 2023
@vercel
Copy link

vercel bot commented Feb 14, 2023

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

Name Status Preview Comments Updated
dgiot-dashboard ❌ Failed (Inspect) Feb 14, 2023 at 6:01AM (UTC)

@pull-checklist
Copy link

Example Check Group #2 (Click here to edit)

  • Modify this checklist and click on the save button for it to appear on Github Pull Requests for this repo
  • If you would like the checklist state to roll up to the Pull Request status, select the Enforce on Merge checkbox

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file Extra Small
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants