-
Notifications
You must be signed in to change notification settings - Fork 2k
ACM-26177: Update branch protections for console repository. #71169
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
base: master
Are you sure you want to change the base?
ACM-26177: Update branch protections for console repository. #71169
Conversation
Signed-off-by: Randy Bruno Piverger <[email protected]>
|
Skipping CI for Draft Pull Request. |
|
@Randy424: This pull request references ACM-26177 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "4.21." or "openshift-4.21.", but it targets "ACM 2.16.0" instead. In 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Randy424 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 |
|
[REHEARSALNOTIFIER] |
| protect: true | ||
| required_pull_request_reviews: | ||
| dismiss_stale_reviews: true | ||
| required_approving_review_count: 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
required_approving_review_count remains at 2.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would change this to 1 since it says 2 on the PR but isn't enforced... and it always trips people up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've had an issue open upstream on this, but no resolution in sight for it:
|
@Randy424: This pull request references ACM-26177 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "4.21." or "openshift-4.21.", but it targets "ACM 2.16.0" instead. In 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 openshift-eng/jira-lifecycle-plugin repository. |
dhaiducek
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I've left a couple comments to consider.
| dismiss_stale_reviews: true | ||
| required_approving_review_count: 2 | ||
| branches: | ||
| release-2.9: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be removed if you want to simplify your configuration--release-2.9 and release-2.10 are no longer supported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree.
| - ci/prow/check | ||
| - ci/prow/images | ||
| - ci/prow/pr-image-mirror | ||
| - ci/prow/pr-image-mirror-mce | ||
| - dco | ||
| - tide |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's fine to leave these here, but Prow will also detect its own jobs and mark them required if you want to leave them off.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, let's keep it simple and only list Konflux jobs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Randy424 We need to include the backplane-* branches as well, and list that they require Konflux checks. This is part of the magic - since we never configure our backplane branch to run PR checks, this will prevent people from checking in directly to a backplane branch instead of the corresponding release branch.


Regarding: https://issues.redhat.com/browse/ACM-26177
Update branch protections to require the correct Konflux jobs to run.