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

[release-4.10] OCPBUGS-24726: snyk code scan exclude vendor directory #61

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #60

/assign Karthik-K-N

Copy link
Contributor

openshift-ci bot commented Nov 7, 2023

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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 kubernetes/test-infra repository. I understand the commands that are listed here.

@Prashanth684 Prashanth684 added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 10, 2023
Copy link
Contributor

openshift-ci bot commented Nov 10, 2023

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-cherrypick-robot

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

@Prashanth684 Prashanth684 added lgtm Indicates that a PR is ready to be merged. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Nov 22, 2023
@Karthik-K-N
Copy link
Member

/retitle [release-4.10] MULTIARCH-4031: snyk code scan exclude vendor directory

@openshift-ci openshift-ci bot changed the title [release-4.10] NO-ISSUE: snyk code scan exclude vendor directory [release-4.10] [MULTIARCH-4031](https://issues.redhat.com/browse/MULTIARCH-4031): snyk code scan exclude vendor directory Nov 28, 2023
@Karthik-K-N
Copy link
Member

/retitle [release-4.10] [MULTIARCH-4031]: snyk code scan exclude vendor directory

@openshift-ci openshift-ci bot changed the title [release-4.10] [MULTIARCH-4031](https://issues.redhat.com/browse/MULTIARCH-4031): snyk code scan exclude vendor directory [release-4.10] [MULTIARCH-4031]: snyk code scan exclude vendor directory Nov 28, 2023
@Karthik-K-N
Copy link
Member

/jira refresh

@openshift-ci-robot
Copy link

@Karthik-K-N: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to this:

/jira refresh

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 kubernetes/test-infra repository.

@Karthik-K-N
Copy link
Member

Karthik-K-N commented Nov 28, 2023

/retitle [release-4.10] MULTIARCH-4031: snyk code scan exclude vendor directory

@openshift-ci openshift-ci bot changed the title [release-4.10] [MULTIARCH-4031]: snyk code scan exclude vendor directory [release-4.10] MULTIARCH-4031: snyk code scan exclude vendor directory Nov 28, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 28, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 28, 2023

@openshift-cherrypick-robot: This pull request references MULTIARCH-4031 which is a valid jira issue.

In response to this:

This is an automated cherry-pick of #60

/assign Karthik-K-N

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 kubernetes/test-infra repository.

@jaypoulz jaypoulz changed the title [release-4.10] MULTIARCH-4031: snyk code scan exclude vendor directory [release-4.10] OCPBUGS-24726: snyk code scan exclude vendor directory Dec 11, 2023
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Dec 11, 2023
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-24726, which is invalid:

  • expected dependent Jira Issue OCPBUGS-24724 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #60

/assign Karthik-K-N

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 kubernetes/test-infra repository.

@jaypoulz
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 11, 2023
@openshift-ci-robot
Copy link

@jaypoulz: This pull request references Jira Issue OCPBUGS-24726, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.10.z) matches configured target version for branch (4.10.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-24724 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-24724 targets the "4.11.z" version, which is one of the valid target versions: 4.11.0, 4.11.z
  • bug has dependents

In response to this:

/jira refresh

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 kubernetes/test-infra repository.

@openshift-merge-bot openshift-merge-bot bot merged commit fba6889 into openshift:release-4.10 Dec 11, 2023
7 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-24726: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-24726 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #60

/assign Karthik-K-N

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 kubernetes/test-infra repository.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-powervs-machine-controllers-container-v4.10.0-202312160824.p0.gfba6889.assembly.stream for distgit ose-powervs-machine-controllers.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants