-
Notifications
You must be signed in to change notification settings - Fork 19
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
Baseline MAINTAINERS, CODEOWNERS, and external collaborator permissions #28
Comments
@samuel-oci, could you please revoke admin access from clients group? |
Hi @anasalkouz , I don't think I have the capability to do so at the moment, perhaps I need to be able another permission to see all other admins? |
@dblock Could you please help on this? neither I nor @samuel-oci has access. |
@bbarani I don't have access either, help? |
I am not seeing the setting tab to view the current list of maintainers as well. @samuel-oci can you try to add the team @opensearch-project/admin team as admin user? I will reach out to the OpenSearch repository orgnaization owners if you are not able to do it. |
@admin changed to have Admin perms. |
I added the named maintainers as maintainers in the guithub permssions. @samuel-oci can you take a look and confirm the changes are okay? |
Hi William,Unfortunately I have out of town with not much internet access until 04/17, can check when I’m back.Thanks,SamSent from my iPhoneOn Apr 7, 2023, at 6:51 PM, William Beckler ***@***.***> wrote:
I added the named maintainers as maintainers in the guithub permssions. @samuel-oci can you take a look and confirm the changes are okay?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@peternied changes looks good to me. |
I think we can resolve the issue now. |
Thanks, verified. |
Follow opensearch-project/.github#125 to baseline MAINTAINERS, CODEOWNERS, and external collaborator permissions.
Close this issue when:
If this repo's permissions was already baselined, please confirm the above when closing this issue.
The text was updated successfully, but these errors were encountered: