Skip to content

Conversation

@HarveyYu-atlas
Copy link

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
  • The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
  • I've signed my commits with DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My builds are green. Try syncing with master if they are not.
  • My organization is added to USERS.md.

@sonarqubecloud
Copy link

@github-actions
Copy link
Contributor

Published E2E Test Results

  4 files    4 suites   3h 25m 56s ⏱️
117 tests 108 ✅  7 💤 2 ❌
472 runs  440 ✅ 28 💤 4 ❌

For more details on these failures, see this check.

Results for commit da116ba.

@github-actions
Copy link
Contributor

Published Unit Test Results

2 368 tests   2 367 ✅  3m 3s ⏱️
  129 suites      0 💤
    1 files        1 ❌

For more details on these failures, see this check.

Results for commit da116ba.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant