You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it looks like it has Write access, but the original idea was just for Read #670 (comment)
Is there a reason the Bot still needs Write access? It might change if #1008 goes forward, but right now it looks like it doesn't need it.
Right now it looks like it's only used by this repo, but with nodejs/admin#471 maybe it will be re-used
We just reused one that already existed. I think it would be fine getting a more restricted one for this one as long as it still has access to write comments
@LaurentGoderre now that I think of it, I don't think it even needs "Read", since it's a public repo, so any user should be able to make comments on the issues (that isn't locked).
Activity
LaurentGoderre commentedon Feb 24, 2020
We just reused one that already existed. I think it would be fine getting a more restricted one for this one as long as it still has access to write comments
nschonni commentedon Feb 24, 2020
@LaurentGoderre now that I think of it, I don't think it even needs "Read", since it's a public repo, so any user should be able to make comments on the issues (that isn't locked).
LaurentGoderre commentedon Feb 27, 2020
True but it should still be a bot with a token. It could be a token with no special access.