Skip to content

Backport of update redhat registry id into release/1.0.x#2443

Closed
hc-github-team-consul-core wants to merge 2 commits intorelease/1.0.xfrom
backport/ci/update-redhat-registry-id/shortly-legible-tadpole
Closed

Backport of update redhat registry id into release/1.0.x#2443
hc-github-team-consul-core wants to merge 2 commits intorelease/1.0.xfrom
backport/ci/update-redhat-registry-id/shortly-legible-tadpole

Conversation

@hc-github-team-consul-core
Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #2337 to be assessed for backporting due to the inclusion of the label backport/1.0.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@curtbushko
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul-k8s/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


Changes proposed in this PR:

How I've tested this PR:

How I expect reviewers to test this PR:

Checklist:

  • Tests added
  • CHANGELOG entry added

    HashiCorp engineers only, community PRs should not add a changelog entry.
    Entries should use present tense (e.g. Add support for...)


Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/ci/update-redhat-registry-id/shortly-legible-tadpole branch from 3b13ab2 to ffffd1b Compare June 23, 2023 17:17
@hashicorp-cla
Copy link
Copy Markdown

hashicorp-cla commented Jun 23, 2023

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


1 out of 2 committers have signed the CLA.

  • curtbushko
  • temp

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

@curtbushko curtbushko self-requested a review June 23, 2023 19:32
@curtbushko curtbushko marked this pull request as ready for review June 23, 2023 19:32
@curtbushko curtbushko enabled auto-merge (squash) June 23, 2023 19:34
@curtbushko
Copy link
Copy Markdown
Contributor

Closing because of CLA

@curtbushko curtbushko closed this Jun 26, 2023
auto-merge was automatically disabled June 26, 2023 14:18

Pull request was closed

@curtbushko curtbushko deleted the backport/ci/update-redhat-registry-id/shortly-legible-tadpole branch January 9, 2024 15:33
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.

3 participants