-
Notifications
You must be signed in to change notification settings - Fork 60
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
Document required permissions #47
Comments
+1 - after removing the github url per #40, the action runs without indication that the lack of permissions is preventing it from labeling PRs, which led me here. |
Good one. Thanks for opening the issue and providing the actual fix for it. you can expect we work on this in the upcoming days/weeks at most. If you want, we would really appreciate opening a PR modifying the current README.md in order to reflect this by default and we would merge it even sooner. Thanks! |
I didn't open a PR yet, because I've used the permission stuff myself for the first time here. So I don't feel comfortable writing any documentation regarding that. I don't even know if any other potential permission defaults might affect my solution, so it only works in my environment and in others more permissions would be needed. I have no idea. My main intent for this Issue was, to provide some information in case someone struggles with the same setup issue and hoping that someone who actually understands what I did would write some documentation eventually. |
@JavierCane I'll do it after work if want to assign it to me. |
adding the permission to the issues actually solved my issue! |
It took me a bit of time to figure out which permissions this actions needs.
In my case, adding the following worked. Maybe that should be added to the README.
The text was updated successfully, but these errors were encountered: