Automate config brancher by auto-config-brancher job at Tue, 21 Apr 2020 11:02:54 UTC - #8447
Merged
openshift-merge-robot merged 1 commit intoApr 21, 2020
Conversation
Contributor
|
@openshift-bot: GitHub didn't allow me to request PR reviews from the following users: ghost. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
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
added
approved
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: openshift-bot The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Contributor
|
@openshift-bot: Updated the following 9 configmaps:
DetailsIn response to this:
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. |
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
/cc @ghost