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

Update fortify/gha-setup-scancentral-client digest to f4282a5 #145

Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 14, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
fortify/gha-setup-scancentral-client action digest 71c3cca -> f4282a5

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.

@performance-testing-bot
Copy link

Unable to locate .performanceTestingBot config file

@viezly
Copy link

viezly bot commented Jun 14, 2023

Pull request by bot. No need to analyze

@senior-dev-bot
Copy link

Hi there! 👋 Thanks for opening a PR. 🎉
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 🚀

@guide-bot
Copy link

guide-bot bot commented Jun 14, 2023

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

  1. Fill out the description.

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

  2. 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
Copy link

difflens bot commented Jun 14, 2023

View changes in DiffLens

@renovate renovate bot changed the title Update fortify/gha-setup-scancentral-client digest to d9f7785 Update fortify/gha-setup-scancentral-client digest to 0dd7fb4 Jun 19, 2023
@renovate renovate bot force-pushed the renovate/fortify-gha-setup-scancentral-client-digest branch from 8819f4e to 3392471 Compare June 19, 2023 13:11
@difflens
Copy link

difflens bot commented Jun 19, 2023

View changes in DiffLens

1 similar comment
@difflens
Copy link

difflens bot commented Jun 19, 2023

View changes in DiffLens

@difflens
Copy link

difflens bot commented Jun 19, 2023

View changes in DiffLens

@renovate renovate bot changed the title Update fortify/gha-setup-scancentral-client digest to 0dd7fb4 Update fortify/gha-setup-scancentral-client digest to f4282a5 Nov 1, 2023
@renovate renovate bot force-pushed the renovate/fortify-gha-setup-scancentral-client-digest branch from 3392471 to c24e221 Compare November 1, 2023 11:16
Copy link

difflens bot commented Nov 1, 2023

View changes in DiffLens

1 similar comment
Copy link

difflens bot commented Nov 1, 2023

View changes in DiffLens

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.

Copy link

difflens bot commented Nov 1, 2023

View changes in DiffLens

1 similar comment
Copy link

difflens bot commented Nov 13, 2023

View changes in DiffLens

Copy link

aviator-app bot commented Dec 3, 2023

Current Aviator status

Aviator will automatically update this comment as the status of the PR changes.
Comment /aviator refresh to force Aviator to re-examine your PR (or learn about other /aviator commands).

This PR was merged manually (without Aviator). Merging manually can negatively impact the performance of the queue. Consider using Aviator next time.


See the real-time status of this PR on the Aviator webapp.
Use the Aviator Chrome Extension to see the status of your PR within GitHub.

Copy link

difflens bot commented Dec 3, 2023

View changes in DiffLens

@AdamOswald AdamOswald merged commit 5ce32b1 into main Feb 7, 2024
16 of 60 checks passed
@AdamOswald AdamOswald deleted the renovate/fortify-gha-setup-scancentral-client-digest branch February 7, 2024 19:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant