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

VAULT-33693 actions: fix push event PR labels #29476

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

ryancragun
Copy link
Collaborator

@ryancragun ryancragun commented Jan 31, 2025

Description

Fix pull request label metadata when triggered by push event types. We now use Github's associatedPullRequests() connection on the Commit associated with the SHA to resolve the labels.

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

@ryancragun ryancragun added pr/no-changelog pr/no-milestone backport/ent/1.16.x+ent Changes are backported to 1.16.x+ent backport/1.18.x backport/ent/1.17.x+ent Changes are backported to 1.17.x+ent labels Jan 31, 2025
@ryancragun ryancragun requested a review from a team as a code owner January 31, 2025 19:14
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jan 31, 2025
@ryancragun
Copy link
Collaborator Author

ryancragun commented Jan 31, 2025

image

An example of the equivalent query manually. In this case we're looking for the labels associated with release SHA for Vault 1.18.4+ent and it correctly resolves the build/all label that we expect to see.

@ryancragun ryancragun changed the title VAULT-33693: actions: fix push event PR labels VAULT-33693 actions: fix push event PR labels Jan 31, 2025
rebwill
rebwill previously approved these changes Jan 31, 2025
Copy link

CI Results:
All Go tests succeeded! ✅

Copy link

Build Results:
All builds succeeded! ✅

tvo0813
tvo0813 previously approved these changes Jan 31, 2025
charlesn-hc
charlesn-hc previously approved these changes Jan 31, 2025
@ryancragun
Copy link
Collaborator Author

Simplified the query a bit more and made it easier to pull out for local exec

Fix pull request label metadata when triggered `push` event types.
We now use Github's `associatedPullRequests()` connection on the
`Commit` associated with the SHA to resolve the labels.

Signed-off-by: Ryan Cragun <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/ent/1.16.x+ent Changes are backported to 1.16.x+ent backport/ent/1.17.x+ent Changes are backported to 1.17.x+ent backport/1.18.x backport/1.19.x hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog pr/no-milestone
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants