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

Jump to bottom

Bump XunitXml.TestLogger from 3.0.70 to 3.0.78 #19066

Merged
merged 1 commit into from Jan 31, 2023
Merged

Bump XunitXml.TestLogger from 3.0.70 to 3.0.78 #19066

merged 1 commit into from Jan 31, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 31, 2023

Bumps XunitXml.TestLogger from 3.0.70 to 3.0.78.

Release notes

Sourced from XunitXml.TestLogger's releases.

v3.0.78

  • Update core testlogger to 3.0.86 for xunit test adapter
  • Fix: Explicit tests should be marked as Skipped. See spekt/nunit.testlogger#86
  • Replace Test Case name parser Possible Breaking Change
Changelog

Sourced from XunitXml.TestLogger's changelog.

v3.0.78 - 2023/01/30

  • Update core testlogger to 3.0.86 for xunit test adapter
  • Fix: Explicit tests should be marked as Skipped. See spekt/nunit.testlogger#86
  • Replace Test Case name parser Possible Breaking Change
Commits

Dependabot compatibility score

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
Bump XunitXml.TestLogger from 3.0.70 to 3.0.78
f448709 
Bumps [XunitXml.TestLogger](https://github.com/spekt/xunit.testlogger) from 3.0.70 to 3.0.78.
- [Release notes](https://github.com/spekt/xunit.testlogger/releases)
- [Changelog](https://github.com/spekt/xunit.testlogger/blob/master/CHANGELOG.md)
- [Commits](spekt/xunit.testlogger@v3.0.70...v3.0.78)

---
updated-dependencies:
- dependency-name: XunitXml.TestLogger
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Jan 31, 2023
@pull-request-quantifier
Copy link

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:
.csproj : +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? 👍  👌  👎 (Email)
Customize PullRequestQuantifier for this repository.

@TravisEz13 TravisEz13 merged commit 337c865 into master Jan 31, 2023
40 checks passed
@TravisEz13 TravisEz13 deleted the dependabot/nuget/XunitXml.TestLogger-3.0.78 branch January 31, 2023 19:31
@msftbot
Copy link

msftbot bot commented Mar 14, 2023

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

Handy links:

gregsdennis pushed a commit to gregsdennis/PowerShell that referenced this pull request Mar 15, 2023
@dependabot @gregsdennis
Bump XunitXml.TestLogger from 3.0.70 to 3.0.78 (PowerShell#19066)
45d9069 
Bumps [XunitXml.TestLogger](https://github.com/spekt/xunit.testlogger) from 3.0.70 to 3.0.78.
- [Release notes](https://github.com/spekt/xunit.testlogger/releases)
- [Changelog](https://github.com/spekt/xunit.testlogger/blob/master/CHANGELOG.md)
- [Commits](spekt/xunit.testlogger@v3.0.70...v3.0.78)

---
updated-dependencies:
- dependency-name: XunitXml.TestLogger
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@TravisEz13 TravisEz13 TravisEz13 approved these changes

@daxian-dbw daxian-dbw

@adityapatwardhan adityapatwardhan

@anmenaga anmenaga

@PaulHigin PaulHigin

Assignees

@daxian-dbw daxian-dbw

Labels
CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log Extra Small
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@TravisEz13 @daxian-dbw