-
Notifications
You must be signed in to change notification settings - Fork 17
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
Trigger requires public JuliaLang membership #133
Comments
The culprit is actually GitHub.jl, which ignores comments from non-collaborators: https://github.com/JuliaWeb/GitHub.jl/blob/809994e91a12f8b7b060d6345d9cc6f22d9d6786/src/activity/events.jl#L178-L192 I'm not sure GitHub.jl should do this, it should be up to the caller to determine whether a trigger is authorized... |
It ignores comments if specified by the user by kwarg, but the bot user nanosoldier only has public access to see the membership list because we did not give it more access |
I know about the kwarg, but I don't think GitHub.jl should be doing this. Regardless of this and the perms to see private membership, I'd like to make it possible to make (public) members of the triage team start Nanosoldier as well. |
Members of the triage team ( |
I think you have to be an admin to see the list of other members on Github? |
I don't think that's the case, at least not if the user has publicized their membership. |
Apparently one doesn't have to be member of JuliaLang at all, anymore. I don't recall making that change, however, how that we support PkgEval on non-julia repositories, we can't just add it back. Maybe it should just check membership of the org that owns the repository being tested? |
It shouldn't, because the bot generally has access to a token to check private membership. Triage team membership should probably be sufficient.
The text was updated successfully, but these errors were encountered: