Bump sudo-bot/action-pull-request-merge from 1.1.1 to 1.2.0

dependabot[bot] commented 2 years ago

Bumps sudo-bot/action-pull-request-merge from 1.1.1 to 1.2.0.

Release notes

Sourced from sudo-bot/action-pull-request-merge's releases.

v1.2.0

Upgrade @actions/core from 1.2.6 to 1.9.0

Upgrade @actions/github from 3.0.0 to 5.0.3

Bump node-fetch from 2.6.0 to 2.6.7 (#12)

Upgrade from node 12 to node 16

New syntax for @actions/github package code (3039d46e5aceaf705c7efce9c1aef3b9597419cb, 5b58b5cb1e46bda23160c3a6d56beeec7036c7e2)

Changelog

Sourced from sudo-bot/action-pull-request-merge's changelog.

[v1.2.0] - 2022-07-10

Upgrade @actions/core from 1.2.6 to 1.9.0

Upgrade @actions/github from 3.0.0 to 5.0.3

Bump node-fetch from 2.6.0 to 2.6.7

Upgrade from node 12 to node 16

Commits

5b58b5c fix: new syntax for @actions/github package code (left overs)
3039d46 fix: new syntax for @actions/github package code
e80b383 chore: bump version number to 1.2.0
c35e2a9 chore: upgrade from node 12 to node 16
4030af4 chore: bump dependencies
b9b1b8d docs: update my website link
f5a85f7 ci: bump actions to v3
cafab7f chore(deps): bump node-fetch from 2.6.0 to 2.6.7
27a6cb6 Update actions
bb66ecc Update node_modules content after update of @actions/core
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[bot] commented 2 years ago

The following labels could not be found: :arrow_up: dependencies.

pull-request-quantifier-deprecated[bot] commented 2 years 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: .yml : +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 detetcted. - 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.

netlify[bot] commented 2 years ago

Deploy Preview for ajaymehta processing.

Name	Link
Latest commit	56ff8f1352cf0db27da23eead4e56c4dfce5bee5
Latest deploy log	https://app.netlify.com/sites/ajaymehta/deploys/62cb81438d8c34000a26bd81

AjayKMehta / blog