Skip to content
This repository was archived by the owner on Feb 24, 2023. It is now read-only.

fix(deps): bump EndBug/label-sync from 2.1.0 to 2.3.1 #158

Closed
wants to merge 1 commit into from
Closed

fix(deps): bump EndBug/label-sync from 2.1.0 to 2.3.1 #158

wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 18, 2022

Bumps EndBug/label-sync from 2.1.0 to 2.3.1.

Release notes

Sourced from EndBug/label-sync's releases.

v2.3.1

What's Changed

New Contributors

Full Changelog: EndBug/label-sync@v2.3.0...v2.3.1

v2.3.0

What's Changed

New Contributors

Full Changelog: EndBug/label-sync@v2.2.0...v2.3.0

v2.2.0

What's Changed

New Contributors

Full Changelog: EndBug/label-sync@v2.1.0...v2.2.0

Commits
  • 3478705 2.3.1
  • 4e21104 chore: update contact email
  • d53c295 docs: add carrodher as a contributor for code (#161)
  • a34bcf8 fix: bump NodeJS version to 16 (#159)
  • 367006f chore(deps): bump @​actions/core from 1.9.1 to 1.10.0 (#157)
  • 0e22eb8 chore(deps-dev): bump typescript from 4.8.3 to 4.8.4 (#156)
  • cd304dc chore(deps-dev): bump typescript from 4.8.2 to 4.8.3 (#155)
  • 6128cc1 ci: update stale workflow
  • 0db641c ci: replace probot with workflow
  • 6043621 chore(deps-dev): bump typescript from 4.7.4 to 4.8.2 (#154)
  • 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)

@dependabot
fix(deps): bump EndBug/label-sync from 2.1.0 to 2.3.1
13f47a9 
Bumps [EndBug/label-sync](https://github.com/EndBug/label-sync) from 2.1.0 to 2.3.1.
- [Release notes](https://github.com/EndBug/label-sync/releases)
- [Commits](EndBug/label-sync@v2.1.0...v2.3.1)

---
updated-dependencies:
- dependency-name: EndBug/label-sync
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update Github_actions code labels Oct 18, 2022
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 18, 2022

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/158/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
Copy link

pull-request-quantifier-deprecated bot commented Oct 18, 2022

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:
.yml : +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.

@dependabot dependabot bot mentioned this pull request Oct 18, 2022
Closed
@dependabot dependabot bot requested review from GregoireF and versnic October 18, 2022 00:24
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 16, 2022

Superseded by #170.

@dependabot dependabot bot closed this Nov 16, 2022
@dependabot dependabot bot deleted the dependabot/github_actions/EndBug/label-sync-2.3.1 branch November 16, 2022 00:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@GregoireF GregoireF Awaiting requested review from GregoireF

@versnic versnic Awaiting requested review from versnic

Assignees

@GregoireF GregoireF

@versnic versnic

Labels

dependencies Pull requests that update a dependency file Extra Small github_actions Pull requests that update Github_actions code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@GregoireF @versnic