chore(deps): update amannn/action-semantic-pull-request action to v5.3.0

renovate[bot] commented 8 months ago

This PR contains the following updates:

Package	Type	Update	Change
amannn/action-semantic-pull-request	action	minor	`v5.2.0` -> `v5.3.0`

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

Release Notes

amannn/action-semantic-pull-request (amannn/action-semantic-pull-request)

### [`v5.3.0`](https://togithub.com/amannn/action-semantic-pull-request/releases/tag/v5.3.0) [Compare Source](https://togithub.com/amannn/action-semantic-pull-request/compare/v5.2.0...v5.3.0) ##### Features - Use Node.js 20 in action ([#240](https://togithub.com/amannn/action-semantic-pull-request/issues/240)) ([4c0d5a2](https://togithub.com/amannn/action-semantic-pull-request/commit/4c0d5a21fc86635c67cc57ffe89d842c34ade284))

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

viezly[bot] commented 8 months ago

Pull request by bot. No need to analyze

performance-testing-bot[bot] commented 8 months ago

Unable to verify url with installation ID

guide-bot[bot] commented 8 months ago

Thanks for opening this Pull Request! We need you to:

Fill out the description.

Action: Edit description and replace <!- ... --> with actual values.
Complete the activities.

Action: Complete If you want to rebase/retry this PR, check this box

If an activity is not applicable, use '\~activity description\~' to mark it not applicable.

difflens[bot] commented 8 months ago

View changes in DiffLens

senior-dev-bot[bot] commented 8 months ago

Hi there! :wave: Thanks for opening a PR. :tada: To get the most out of Senior Dev, please uninstall the app from your organization, then re-install it into your organization. You can uninstall the app here :rocket:

renovate[bot] commented 8 months ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v5.3.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

sonarcloud[bot] commented 8 months ago

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

pull-request-quantifier-deprecated[bot] commented 8 months 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 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.

AdamOswald / face