Skip to content

NO-ISSUE: fix rebase branch name for GH query - #1346

Merged
openshift-merge-robot merged 1 commit into
openshift:release-4.12from
pmtk:patch-5
Feb 13, 2023
Merged

NO-ISSUE: fix rebase branch name for GH query#1346
openshift-merge-robot merged 1 commit into
openshift:release-4.12from
pmtk:patch-5

Conversation

@pmtk

@pmtk pmtk commented Feb 9, 2023

Copy link
Copy Markdown
Member

'+' is used in GitHub as a character for joining filters in query and breaks prow.ci.openshift.org PR search

'+' is used in github as a character for joining filters in query and breaks prow.ci.openshift.org pr search
@openshift-ci

openshift-ci Bot commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

@pmtk: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

fix rebase branch name for gh query

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-ci
openshift-ci Bot requested review from copejon and sallyom February 9, 2023 16:12
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 9, 2023
@ggiguash

ggiguash commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2023
@openshift-ci

openshift-ci Bot commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

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

The pull request process is described here

Details 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

@pmtk pmtk changed the title fix rebase branch name for gh query NO-ISSUE: fix rebase branch name for gh query Feb 9, 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 Feb 9, 2023
@openshift-ci-robot

Copy link
Copy Markdown

@pmtk: This pull request explicitly references no jira issue.

Details

In response to this:

'+' is used in GitHub as a character for joining filters in query and breaks prow.ci.openshift.org PR search

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-ci

openshift-ci Bot commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

@pmtk: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

NO-ISSUE: fix rebase branch name for gh query

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.

@pmtk

pmtk commented Feb 9, 2023

Copy link
Copy Markdown
Member Author

/label backport-risk-assessed
/label bugzilla/valid-bug

@openshift-ci openshift-ci Bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Feb 9, 2023
@pmtk pmtk changed the title NO-ISSUE: fix rebase branch name for gh query NO-ISSUE: fix rebase branch name for GH query Feb 9, 2023
@openshift-ci openshift-ci Bot removed the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Feb 9, 2023
@openshift-ci

openshift-ci Bot commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

@pmtk: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

NO-ISSUE: fix rebase branch name for GH query

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.

@dhellmann

Copy link
Copy Markdown
Contributor

/label bugzilla/valid-bug

@openshift-ci openshift-ci Bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Feb 9, 2023
@jogeo

jogeo commented Feb 13, 2023

Copy link
Copy Markdown
Contributor

/label cherry-pick-approved

@openshift-ci openshift-ci Bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 13, 2023
@openshift-ci

openshift-ci Bot commented Feb 13, 2023

Copy link
Copy Markdown
Contributor

@pmtk: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.