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

Bug DFBUGS-1168: [release-4.18-compatibility] Fix yarn.lock from: https://github.com/red-hat-storage/odf-console/pull/1765 #1774

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1772

/assign GowthamShanmugam

Signed-off-by: Gowtham Shanmugasundaram <[email protected]>
@GowthamShanmugam
Copy link
Contributor

GowthamShanmugam commented Dec 16, 2024

/retitle Bug DFBUGS-1168: [release-4.18-compatibility] Fix yarn.lock from: #1765

@openshift-ci openshift-ci bot changed the title [release-4.18-compatibility] Fix yarn.lock from: https://github.com/red-hat-storage/odf-console/pull/1765 Bug DFBUGS-1168: [release-4.18-compatibility] Fix yarn.lock from: https://github.com/red-hat-storage/odf-console/pull/1765 Dec 16, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid jira ticket of any type label Dec 16, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 16, 2024

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-1168](https://issues.redhat.com//browse/DFBUGS-1168), which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED 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.

In response to this:

This is an automated cherry-pick of #1772

/assign GowthamShanmugam

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting label Dec 16, 2024
@GowthamShanmugam
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting label Dec 16, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 16, 2024

@GowthamShanmugam: This pull request references [Jira Issue DFBUGS-1168](https://issues.redhat.com//browse/DFBUGS-1168), which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.18) matches configured target version for branch (odf-4.18)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @PrasadDesala

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting label Dec 16, 2024
Copy link
Contributor

openshift-ci bot commented Dec 16, 2024

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: PrasadDesala.

Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@GowthamShanmugam: This pull request references [Jira Issue DFBUGS-1168](https://issues.redhat.com//browse/DFBUGS-1168), which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.18) matches configured target version for branch (odf-4.18)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @PrasadDesala

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 openshift-eng/jira-lifecycle-plugin repository.

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-sigs/prow repository.

@openshift-ci openshift-ci bot added the lgtm label Dec 16, 2024
Copy link
Contributor

openshift-ci bot commented Dec 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: GowthamShanmugam, 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

@openshift-merge-bot openshift-merge-bot bot merged commit b22320f into red-hat-storage:release-4.18-compatibility Dec 16, 2024
7 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 16, 2024

@openshift-cherrypick-robot: [Jira Issue DFBUGS-1168](https://issues.redhat.com//browse/DFBUGS-1168): All pull requests linked via external trackers have merged:

[Jira Issue DFBUGS-1168](https://issues.redhat.com//browse/DFBUGS-1168) has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #1772

/assign GowthamShanmugam

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved jira/valid-bug Indicates that the 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants