-
-
Notifications
You must be signed in to change notification settings - Fork 17
2021-10-26 notes #47
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
2021-10-26 notes #47
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌
Sure, or we could delete that line. Co-authored-by: Jacob Smith <3012099+JakobJingleheimer@users.noreply.github.com>
O.o weird. why does my approval not fully register anymore? (it says "1 approval", and the checkmark next to my seemingly unofficial approval is greyed out instead of green) |
@JakobJingleheimer, perhaps because you are not a core collaborator, but if anyone knows how to give you commit access to this repo, it seems like that would be appropriate at this point. That privilege should probably also be extended to all of the other team members as well, but I don't know how to do it. It used to be possible, but I can't seem to find the settings necessary to grant others this power. (?) If anyone can find out how (perhaps in the GitHub docs), I would gladly give you all the commit bit. |
I surely already have "Write" permissions, which is supposed to enable
I would have guessed "manage issues and pull requests" would include approving, but perhaps not. So maybe it takes granting "Maintain" permissions on this repo (to the P.S. I already have 2FA set up (I think membership in the nodejs org requires that anyway). |
I think it’s probably just because I committed your suggestion after you had approved the PR. So your approval was for an earlier version of this PR, not the current one. I bet if you approve again now, it’ll appear as green. |
This looks like a github bug. I would try to contact support if it isn't resolved today |
From GitHub support:
So perhaps I/we could have the next-up level of permissions on this repo? |
It looks like the cc @MylesBorins |
Closes #45