Skip to content
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

*: Add platform owners #2782

Merged

Conversation

abhinavdahiya
Copy link
Contributor

Adding platform owners helps increase the people should help reduce bottleneck on installer-approvers

/assign @sdodson
/cc @openshift/openshift-team-installer
/cc @stbenjam @hardys

`<platform>-approvers` and `<platform>-reviewers` alias from `OWNER_ALIASES` should be used to maintain membership.
This adds various people to platform owners
@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Dec 10, 2019
@abhinavdahiya
Copy link
Contributor Author

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 10, 2019
baremetal-reviewers:
- celebdor
- markmc
- russellb
- hardys
- stbenjam
aws-approvers:
- patrickdillon
Copy link
Member

Choose a reason for hiding this comment

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

If we drop auto approval we'll need to add a second here so PRs from @patrickdillon aren't blocked.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

well i'm thinking we should use the -approvers as additive to installer-approvers to reduce duplication...

@sdodson
Copy link
Member

sdodson commented Dec 10, 2019

/approve
I'm definitely in favor of federating review and approval.
What's the behavior of empty reviewers aliases? Does that just default back to allowing lgtm from organization members?

@abhinavdahiya
Copy link
Contributor Author

What's the behavior of empty reviewers aliases? Does that just default back to allowing lgtm from organization members?
https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md#owners

reviewers: a list of GitHub usernames or aliases that are good candidates to /lgtm a PR

it is used to find good candidates, and doesn't affect actually who can lgtm.

@abhinavdahiya
Copy link
Contributor Author

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 11, 2019
@abhinavdahiya
Copy link
Contributor Author

/retest

@sdodson
Copy link
Member

sdodson commented Dec 11, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 11, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, sdodson

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:
  • OWNERS [abhinavdahiya,sdodson]

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

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@abhinavdahiya
Copy link
Contributor Author

/retest

1 similar comment
@abhinavdahiya
Copy link
Contributor Author

/retest

@openshift-merge-robot openshift-merge-robot merged commit 789b53e into openshift:master Dec 12, 2019
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. retest-not-required-docs-only size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants