NO-ISSUE: add jiazha to approvers

[jianzhangbjz]

It seems that #457 doesn’t work as expected based on #467 (comment). Therefore, I’ve created a new PR to add the QE leader to the downstream approvers.

[openshift-ci-robot]

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

Details

In response to this:

It seems that #457 doesn’t work as expected based on #467 (comment). Therefore, I’ve created a new PR to add the QE leader to the downstream approvers.

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.

[jianzhangbjz]

Hi @tmshort@perdasilva , could you help approve it when you get a chance? Thanks!

[jianzhangbjz]

/test e2e-aws-techpreview-olmv1-ext

[jianzhangbjz]

/retest-required

[jianzhangbjz]

/verified by pass

[openshift-ci-robot]

@jianzhangbjz: This PR has been marked as verified by pass.

Details

In response to this:

/verified by pass

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.

[tmshort]

/verify-owners

[tmshort]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jianzhangbjz, tmshort

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:

• DOWNSTREAM_OWNERS [tmshort]

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

[tmshort]

/test e2e-aws-techpreview-olmv1-ext
/test okd-scos-e2e-aws-ovn

[tmshort]

/lgtm

[openshift-ci]

@jianzhangbjz: 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-sigs/prow repository. I understand the commands that are listed here.

[jianzhangbjz]

/cherry-pick release-4.20

[jianzhangbjz]

/cherry-pick release-4.19

[jianzhangbjz]

/cherry-pick release-4.18

[jianzhangbjz]

/cherry-pick release-4.17

[openshift-cherrypick-robot]

@jianzhangbjz: new pull request created: #513

Details

In response to this:

/cherry-pick release-4.20

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-cherrypick-robot]

@jianzhangbjz: #477 failed to apply on top of branch "release-4.19":

Applying: UPSTREAM: <carry>: add jiazha to approvers
Using index info to reconstruct a base tree...
M	DOWNSTREAM_OWNERS_ALIASES
Falling back to patching base and 3-way merge...
Auto-merging DOWNSTREAM_OWNERS_ALIASES
CONFLICT (content): Merge conflict in DOWNSTREAM_OWNERS_ALIASES
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 UPSTREAM: <carry>: add jiazha to approvers

Details

In response to this:

/cherry-pick release-4.19

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-cherrypick-robot]

@jianzhangbjz: #477 failed to apply on top of branch "release-4.18":

Applying: UPSTREAM: <carry>: add jiazha to approvers
Using index info to reconstruct a base tree...
M	DOWNSTREAM_OWNERS_ALIASES
Falling back to patching base and 3-way merge...
Auto-merging DOWNSTREAM_OWNERS_ALIASES
CONFLICT (content): Merge conflict in DOWNSTREAM_OWNERS_ALIASES
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 UPSTREAM: <carry>: add jiazha to approvers

Details

In response to this:

/cherry-pick release-4.18

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-cherrypick-robot]

@jianzhangbjz: #477 failed to apply on top of branch "release-4.17":

Applying: UPSTREAM: <carry>: add jiazha to approvers
Using index info to reconstruct a base tree...
M	DOWNSTREAM_OWNERS_ALIASES
Falling back to patching base and 3-way merge...
Auto-merging DOWNSTREAM_OWNERS_ALIASES
CONFLICT (content): Merge conflict in DOWNSTREAM_OWNERS_ALIASES
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 UPSTREAM: <carry>: add jiazha to approvers

Details

In response to this:

/cherry-pick release-4.17

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.