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

Backport of ci: don't verify s390x into release/1.15.x #18225

Conversation

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

Backport

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

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


Description

Our verification process requires running the binary. We have no hardware to do this for s390x, so we can't verify.


Overview of commits

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@github-actions github-actions bot added type/ci Relating to continuous integration (CI) tooling for testing or releases theme/contributing Additions and enhancements to community contributing materials labels Jul 21, 2023
@vercel vercel bot temporarily deployed to Preview – consul-ui-staging July 21, 2023 17:04 Inactive
@vercel vercel bot temporarily deployed to Preview – consul July 21, 2023 17:06 Inactive
@hc-github-team-consul-core hc-github-team-consul-core merged commit b59f512 into release/1.15.x Jul 21, 2023
108 checks passed
@hc-github-team-consul-core hc-github-team-consul-core deleted the backport/loshz-patch-1/purely-promoted-gar branch July 21, 2023 17:20
@jira jira bot mentioned this pull request Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme/contributing Additions and enhancements to community contributing materials type/ci Relating to continuous integration (CI) tooling for testing or releases
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants