generated from ipdxco/github-as-code
-
Notifications
You must be signed in to change notification settings - Fork 28
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
[General] mergify permissions #251
Comments
cc @galargh do you see the link and what the permissions are? |
@andyschwab are you able to see the link? |
@aschmahmann, let me know if we're good to execute 👍 |
@andyschwab please execute the mergify one. |
Updated permissions have been accepted for Mergify. Mergify currently has access to a single repository: rust-libp2p |
I'm closing this issue as done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
We are facing mergify issues with branch protections webhooks with
rust-libp2p
, and @jxs has opened a ticket with Mergify support. Their answer wasThey said they cannot resend the link to accept the additional permissions to an external email
We are unable to view the link since we are not admin of the libp2p Github org.
Why do you need this?
Fix Mergify on
rust-libp2p
What else do we need to know?
It would be perfect if an admin could approve the additional permissions (if reasonable), otherwise we could promote @jxs or myself temporarily so that we accept the permissions.
DRI: myself
The text was updated successfully, but these errors were encountered: