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

access for triagers for project boards #542

Merged
merged 2 commits into from
Nov 5, 2020

Conversation

SergeyKanzhelev
Copy link
Member

Based on this conversation: #525 (comment)

@SergeyKanzhelev
Copy link
Member Author

Also created ticket with GitHub asking why Write permissions are needed https://support.github.com/ticket/personal/0/872841

Comment on lines +28 to +31
have access to the Project Boards. Note, by not adding members of `foo-triagers` to
CODEOWNERS file, repository restricts triagers from counting a triagers approvals for
PRs. See the [Policies](#policies) section that suggest to ensure that `Require
review from Code Owners` is checked.
Copy link
Member

Choose a reason for hiding this comment

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

I think their approvals will still count for the minimum number of required approvals (by members with write access) and the code owner check will pass even if only one single code owner has approved.

Copy link
Member Author

Choose a reason for hiding this comment

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

yes, it still will be green. But at least some level of distinction between two roles may give some confidence to maintainers. Do you think some rewording is needed here? Or an additional note?

I hope that GitHub can change this =)

Copy link
Member

Choose a reason for hiding this comment

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

I just wanted to point this out in case it was missed but if there's no way to work around this restriction I think it's fine.

@SergeyKanzhelev SergeyKanzhelev merged commit ae9421e into master Nov 5, 2020
@SergeyKanzhelev SergeyKanzhelev deleted the SergeyKanzhelev-patch-2 branch November 5, 2020 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants