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

CI(release): tune Storage & Compute release PR title #7870

Merged
merged 1 commit into from
May 24, 2024

Conversation

bayandin
Copy link
Member

Problem

A title for automatic proxy release PRs is Proxy release, and for storage & compute it's just Release

Summary of changes

  • Amend PR title for Storage & Compute releases to "Storage & Compute release"

Checklist before requesting a review

  • I have performed a self-review of my code.
  • If it is a core feature, I have added thorough tests.
  • Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
  • If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

  • Do not forget to reformat commit message to not include the above checklist

Copy link

3114 tests run: 2987 passed, 0 failed, 127 skipped (full report)


Flaky tests (1)

Postgres 15

  • test_vm_bit_clear_on_heap_lock: debug

Code coverage* (full report)

  • functions: 31.4% (6445 of 20541 functions)
  • lines: 48.3% (49845 of 103239 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
db7a3f8 at 2024-05-23T22:29:03.144Z :recycle:

@bayandin bayandin requested a review from jcsp May 24, 2024 10:11
@bayandin bayandin changed the title CI(release): tune Storage & Compute release title CI(release): tune Storage & Compute release PR title May 24, 2024
@bayandin bayandin merged commit 71a7fd9 into main May 24, 2024
66 of 67 checks passed
@bayandin bayandin deleted the bayandin/tune-storage-release-message branch May 24, 2024 13:11
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.

2 participants