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.

Sign up for GitHub

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

Jump to bottom

SECURESIGN-568: Extend Rekor API to support sharding configuration #512

Merged
merged 1 commit into from
Jul 30, 2024
Merged

SECURESIGN-568: Extend Rekor API to support sharding configuration #512

merged 1 commit into from
Jul 30, 2024

Conversation

osmman
Copy link
Contributor

@osmman osmman commented Jul 17, 2024

No description provided.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 17, 2024 •
edited by openshift-ci bot
Loading

@osmman: This pull request references SECURESIGN-568 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.17.0" version, but no target version was set.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jul 17, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: osmman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@osmman osmman force-pushed the SECURESIGN-568 branch 2 times, most recently from efb2600 to f33fcd3 Compare July 17, 2024 12:33
@osmman osmman requested review from lance and bouskaJ July 17, 2024 12:53
@osmman osmman mentioned this pull request Jul 17, 2024
Merged
@osmman osmman requested a review from bouskaJ July 26, 2024 10:08
@osmman osmman force-pushed the SECURESIGN-568 branch 4 times, most recently from 1dcaf20 to 0aece5b Compare July 26, 2024 12:17
@osmman osmman requested a review from bouskaJ July 29, 2024 09:51
@bouskaJ
Copy link
Collaborator

bouskaJ commented Jul 30, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Jul 30, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit b632634 into main Jul 30, 2024
15 checks passed
@osmman osmman deleted the SECURESIGN-568 branch September 17, 2024 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sabre1041 sabre1041 Awaiting requested review from sabre1041

@tommyd450 tommyd450 Awaiting requested review from tommyd450

@lance lance Awaiting requested review from lance

@bouskaJ bouskaJ Awaiting requested review from bouskaJ

Assignees

@bouskaJ bouskaJ

Labels
approved jira/valid-reference lgtm
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@osmman @openshift-ci-robot @bouskaJ