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

fix: make sure a single trace id is used for a single upload #603

Conversation

jd
Copy link
Member

@jd jd commented Jan 22, 2025

Do not use different traces for multiple JUnit

Do not use different traces for multiple JUnit

Change-Id: I271dff71114bab6841aeec85be6d84cf2164528e
Copy link
Contributor

mergify bot commented Jan 22, 2025

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Changelog requirements

Wonderful, this rule succeeded.
  • any of:
    • -title ~= ^feat
    • label = need changelog
    • label = skip changelog

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 🔎 Reviews

Wonderful, this rule succeeded.
  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

@mergify mergify bot requested a review from a team January 22, 2025 14:21
@mergify mergify bot merged commit 3e5e16d into main Jan 23, 2025
5 checks passed
@mergify mergify bot deleted the devs/jd/fix-multi-junit/I271dff71114bab6841aeec85be6d84cf2164528e branch January 23, 2025 08:20
@mergify mergify bot added queued and removed queued labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants