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

Add tool to trigger license information gathering for NuGet modules #18827

Merged
merged 4 commits into from
Jan 31, 2023

Conversation

TravisEz13
Copy link
Member

@TravisEz13 TravisEz13 commented Dec 19, 2022

PR Summary

Add tool to trigger license information gathering for NuGet modules

PR Context

I've been running this tool manually. The goal would be to make the license update PRs only pass if all the information needed is present.

For now, I'm just capturing the work I've done so far.

PR Checklist

@pull-request-quantifier-deprecated

This PR has 160 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Medium
Size       : +160 -0
Percentile : 52%

Total files changed: 4

Change summary by file extension:
.spelling : +2 -0
.ps1 : +33 -0
.md : +19 -0
.psm1 : +106 -0

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.

@ghost ghost added the Review - Needed The PR is being reviewed label Dec 27, 2022
@ghost
Copy link

ghost commented Dec 27, 2022

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

@adityapatwardhan adityapatwardhan added the CL-Tools Indicates that a PR should be marked as a tools change in the Change Log label Jan 31, 2023
@TravisEz13 TravisEz13 merged commit 049a1f2 into PowerShell:master Jan 31, 2023
@TravisEz13 TravisEz13 deleted the clearlydefined branch January 31, 2023 20:58
@ghost ghost removed the Review - Needed The PR is being reviewed label Jan 31, 2023
JamesWTruher pushed a commit to JamesWTruher/PowerShell-1 that referenced this pull request Feb 3, 2023
@ghost
Copy link

ghost commented Feb 24, 2023

🎉v7.3.3 has been released which incorporates this pull request.:tada:

Handy links:

@ghost
Copy link

ghost commented Mar 14, 2023

🎉v7.4.0-preview.2 has been released which incorporates this pull request.:tada:

Handy links:

@ghost
Copy link

ghost commented Jun 27, 2023

🎉v7.2.12 has been released which incorporates this pull request.:tada:

Handy links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backport-7.2.x-Done Backport-7.3.x-Done CL-Tools Indicates that a PR should be marked as a tools change in the Change Log Medium
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants