[pull] main from dotnet:main

[pull]

See Commits and Changes for more details.

---

Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

[commit-lint]

Contributors

jasonmalinowski, CyrusNajmabadi, mavasani

Commit-Lint commands

You can trigger Commit-Lint actions by commenting on this PR:

• @Commit-Lint merge patch will merge dependabot PR on "patch" versions (X.X.Y - Y change)
• @Commit-Lint merge minor will merge dependabot PR on "minor" versions (X.Y.Y - Y change)
• @Commit-Lint merge major will merge dependabot PR on "major" versions (Y.Y.Y - Y change)
• @Commit-Lint merge disable will desactivate merge dependabot PR
• @Commit-Lint review will approve dependabot PR
• @Commit-Lint stop review will stop approve dependabot PR

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[mergify]

@pull-request-quantifier[bot] is not allowed to run commands

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +197892 -60276
Percentile : 100%

Total files changed: 2830

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +507 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +172692 -49980
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +197904 -60281
Percentile : 100%

Total files changed: 2830

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +509 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +172702 -49985
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +196650 -60226
Percentile : 100%

Total files changed: 2821

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +509 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +171448 -49930
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +196650 -60226
Percentile : 100%

Total files changed: 2821

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +509 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +171448 -49930
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +196650 -60226
Percentile : 100%

Total files changed: 2821

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +509 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +171448 -49930
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +196650 -60226
Percentile : 100%

Total files changed: 2821

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +509 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +171448 -49930
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +196650 -60226
Percentile : 100%

Total files changed: 2821

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +509 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +171448 -49930
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +196650 -60226
Percentile : 100%

Total files changed: 2821

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +509 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +171448 -49930
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +196650 -60226
Percentile : 100%

Total files changed: 2821

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +509 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +171448 -49930
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +196650 -60226
Percentile : 100%

Total files changed: 2821

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +509 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +171448 -49930
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Large
Size       : +196650 -60226
Percentile : 100%

Total files changed: 2821

Change summary by file extension:
.json : +981 -420
.editorconfig : +33 -34
.git-blame-ignore-revs : +3 -1
.md : +2951 -242
.yml : +2395 -1695
.gitignore : +3 -1
.sln : +0 -0
.slnf : +34 -27
.targets : +271 -110
.props : +509 -324
.config : +22 -2
.lutconfig : +6 -0
.dic : +4 -0
.txt : +129 -81
.cmd : +4 -0
.sh : +1175 -612
.xml : +708 -149
.gdntsa : +15 -0
.ps1 : +1067 -528
.focal : +24 -0
.jammy : +24 -0
.trusty : +0 -24
.xenial : +10 -2
.patch : +27 -155
.ks : +0 -38
.buster : +2 -0
.bionic : +16 -0
.sid : +1 -0
.cmake : +158 -33
.csproj : +327 -202
.lss : +29 -0
.psm1 : +2 -1
.globalconfig : +34 -4
.reg : +3 -0
.csx : +42 -0
.nuspec : +0 -22
.cs : +171448 -49930
.projitems : +361 -56
.resx : +450 -523
.xlf : +8040 -1981
.vb : +5148 -2915
.vbproj : +44 -45
.ruleset : +0 -16
.xsd : +1 -0
.g4 : +106 -29
.shproj : +17 -17
.devcontainer/Dockerfile : +5 -0
.github/CODEOWNERS : +21 -7

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.