Skip to content

add clnperez as sshd bastion owner for p libvirt - #8564

Merged
openshift-merge-robot merged 1 commit into
openshift:masterfrom
clnperez:clnperez-libvirt-p-admin
May 6, 2020
Merged

add clnperez as sshd bastion owner for p libvirt#8564
openshift-merge-robot merged 1 commit into
openshift:masterfrom
clnperez:clnperez-libvirt-p-admin

Conversation

@clnperez

Copy link
Copy Markdown
Contributor

Signed-off-by: Christy Norman christy@linux.vnet.ibm.com

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 24, 2020
@clnperez
clnperez force-pushed the clnperez-libvirt-p-admin branch from a6067d4 to 76561d1 Compare April 27, 2020 15:33
@clnperez

Copy link
Copy Markdown
Contributor Author

@hamzy @crawford PTAL

Signed-off-by: Christy Norman <christy@linux.vnet.ibm.com>
@clnperez
clnperez force-pushed the clnperez-libvirt-p-admin branch from 76561d1 to 30b8a54 Compare May 6, 2020 19:59

@jaypoulz jaypoulz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe since this is an admin script, it needs to be run manually by somone from the testplatform team for it to take effect. :)

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 6, 2020
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: clnperez, jaypoulz

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

@openshift-merge-robot
openshift-merge-robot merged commit 25b6235 into openshift:master May 6, 2020
@clnperez

clnperez commented May 7, 2020

Copy link
Copy Markdown
Contributor Author

I'm g2g. Thanks @jaypoulz

bryan-cox added a commit to bryan-cox/release that referenced this pull request May 21, 2026
The pipeline controller's lgtm-config only watched the main branch
for openshift/hypershift. This meant e2e jobs using
pipeline_skip_if_only_changed on release-4.22 never triggered because
the controller didn't monitor that branch.

Multiple release-4.22 PRs merged without e2e test coverage (openshift#8564,
openshift#8534, openshift#8447) while the same commits on main got full e2e runs.

Remove the branch filter entirely so all branches are watched,
matching the pattern used by other repos in the config. This prevents
the same issue on future release branches.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
openshift-merge-bot Bot pushed a commit that referenced this pull request May 21, 2026
The pipeline controller's lgtm-config only watched the main branch
for openshift/hypershift. This meant e2e jobs using
pipeline_skip_if_only_changed on release-4.22 never triggered because
the controller didn't monitor that branch.

Multiple release-4.22 PRs merged without e2e test coverage (#8564,
#8534, #8447) while the same commits on main got full e2e runs.

Remove the branch filter entirely so all branches are watched,
matching the pattern used by other repos in the config. This prevents
the same issue on future release branches.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
andrej1991 pushed a commit to andrej1991/release that referenced this pull request Jul 6, 2026
…shift#79626)

The pipeline controller's lgtm-config only watched the main branch
for openshift/hypershift. This meant e2e jobs using
pipeline_skip_if_only_changed on release-4.22 never triggered because
the controller didn't monitor that branch.

Multiple release-4.22 PRs merged without e2e test coverage (openshift#8564,
openshift#8534, openshift#8447) while the same commits on main got full e2e runs.

Remove the branch filter entirely so all branches are watched,
matching the pattern used by other repos in the config. This prevents
the same issue on future release branches.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
TimurMP pushed a commit to TimurMP/release that referenced this pull request Jul 8, 2026
…shift#79626)

The pipeline controller's lgtm-config only watched the main branch
for openshift/hypershift. This meant e2e jobs using
pipeline_skip_if_only_changed on release-4.22 never triggered because
the controller didn't monitor that branch.

Multiple release-4.22 PRs merged without e2e test coverage (openshift#8564,
openshift#8534, openshift#8447) while the same commits on main got full e2e runs.

Remove the branch filter entirely so all branches are watched,
matching the pattern used by other repos in the config. This prevents
the same issue on future release branches.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
SachinNinganure pushed a commit to SachinNinganure/release that referenced this pull request Jul 20, 2026
…shift#79626)

The pipeline controller's lgtm-config only watched the main branch
for openshift/hypershift. This meant e2e jobs using
pipeline_skip_if_only_changed on release-4.22 never triggered because
the controller didn't monitor that branch.

Multiple release-4.22 PRs merged without e2e test coverage (openshift#8564,
openshift#8534, openshift#8447) while the same commits on main got full e2e runs.

Remove the branch filter entirely so all branches are watched,
matching the pattern used by other repos in the config. This prevents
the same issue on future release branches.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
srivickynesh pushed a commit to srivickynesh/release that referenced this pull request Aug 5, 2026
…shift#79626)

The pipeline controller's lgtm-config only watched the main branch
for openshift/hypershift. This meant e2e jobs using
pipeline_skip_if_only_changed on release-4.22 never triggered because
the controller didn't monitor that branch.

Multiple release-4.22 PRs merged without e2e test coverage (openshift#8564,
openshift#8534, openshift#8447) while the same commits on main got full e2e runs.

Remove the branch filter entirely so all branches are watched,
matching the pattern used by other repos in the config. This prevents
the same issue on future release branches.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
malingatembo pushed a commit to malingatembo/release that referenced this pull request Aug 5, 2026
…shift#79626)

The pipeline controller's lgtm-config only watched the main branch
for openshift/hypershift. This meant e2e jobs using
pipeline_skip_if_only_changed on release-4.22 never triggered because
the controller didn't monitor that branch.

Multiple release-4.22 PRs merged without e2e test coverage (openshift#8564,
openshift#8534, openshift#8447) while the same commits on main got full e2e runs.

Remove the branch filter entirely so all branches are watched,
matching the pattern used by other repos in the config. This prevents
the same issue on future release branches.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
TimurMP pushed a commit to TimurMP/release that referenced this pull request Sep 5, 2026
…shift#79626)

The pipeline controller's lgtm-config only watched the main branch
for openshift/hypershift. This meant e2e jobs using
pipeline_skip_if_only_changed on release-4.22 never triggered because
the controller didn't monitor that branch.

Multiple release-4.22 PRs merged without e2e test coverage (openshift#8564,
openshift#8534, openshift#8447) while the same commits on main got full e2e runs.

Remove the branch filter entirely so all branches are watched,
matching the pattern used by other repos in the config. This prevents
the same issue on future release branches.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants