feat: add merge key to analysis template #2842

zachaller · 2023-06-14T15:03:03Z

add analysis template merge key information

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.

github-actions · 2023-06-14T15:29:50Z

Go Published Test Results

1 988 tests 1 988 ✔️ 2m 35s ⏱️
  118 suites       0 💤
      1 files       0 ❌

Results for commit 9ab372e.

♻️ This comment has been updated with latest results.

codecov · 2023-06-14T15:30:08Z

Codecov Report

Patch and project coverage have no change.

Comparison is base (194c656) 81.67% compared to head (9ab372e) 81.67%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2842   +/-   ##
=======================================
  Coverage   81.67%   81.67%           
=======================================
  Files         133      133           
  Lines       20188    20188           
=======================================
  Hits        16489    16489           
  Misses       2847     2847           
  Partials      852      852

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.