-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 owner files for docs/ and test/ #5469
Conversation
38871d0
to
ac19676
Compare
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.
A few nits
ac19676
to
20d4b01
Compare
/lgtm |
20d4b01
to
abfae26
Compare
e0ecb80
to
0cc2bbe
Compare
0cc2bbe
to
3b7d690
Compare
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.
@enxebre thanks for pushing forward this effort!
Only two nits from my side, but overall it looks great
3b7d690
to
025ba51
Compare
OWNERS_ALIASES
Outdated
# ----------------------------------------------------------- | ||
# OWNER_ALIASES for test | ||
# ----------------------------------------------------------- | ||
|
||
cluster-api-test-reviewers: | ||
cluster-api-test-maintainers: |
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.
We should probably split test rather than have a unique one for all the subfolders, CAPD already has its own, maybe let's add one for the test framework?
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.
+1 for having owners specifically for the test framework to start with (as in the library)
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.
If we have one for test/infrastructure/docker and test/framework, should we have another one for test/e2e?
Note: we also have test/infrastructure/container, but it doesn't contain a lot of code.
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'm ok with all the solutions, but I think that also the current solution make sense given that
- owners in
test/
are owners of the test framework, E2E tests but also owners of CAPD that is used extensively in our E2E. - owners in
test/infrastructure/docker
are owner of CAPD only(we can eventually add test/infrastructure/container under the same responsibility now or at later stage)
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.
Ok I updated to include a new OWNERS file in test/framework so:
- Owners in test/ are owners of the test framework, E2E tests but also owners of CAPD that is used extensively in our E2E.
- Owners in test/infrastructure/docker are owner of CAPD only(we can eventually add test/infrastructure/container under the same responsibility now or at later stage)
- Owners in test/framework own the library.
I wouldn't go too far breaking this down until we have root owners in /test so they can figure out the best way for them to operate.
Let me know if that make sense or you want me to change something else.
025ba51
to
95afee9
Compare
95afee9
to
fa3aa14
Compare
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri 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 |
What this PR does / why we need it:
Add owner files for docs/ and test/
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #5456