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, all the Node.js Foundation members marked in PRs as just Member. So there is no clarity sometimes (especially for new collaborators) if this member (there are 545 now) is also a collaborator (there are 94 now), i.e. if they can run a CI or add labels or land a PR etc. and if help needed.
To save it, you can simply select the code (from javascript: { up to the last }) and drag it to the bookmarks panel, then edit the bookmark name.
It also can be used as a user script for Tampermonkey, so the check could be run automatically without clicking on the bookmarklet. See user script header example in the first comment of the gist.
To use the bookmarklet, you should be in the 'Conversation' tab of a PR. It can work on other pages, but this was not tested.
The code simply XMLHttpRequests collaborators page, greps usernames and then marks athor links in the PR page according to the collaborators' usernames list — with green (= a user can ran CI etc.) or grey (= a user can't ran CI etc. for now) colors.
Feel free to fork and adjust anything)
The text was updated successfully, but these errors were encountered:
vsemozhetbyt
added
meta
Issues and PRs related to the general management of the project.
tools
Issues and PRs related to the tools directory.
labels
Apr 8, 2017
Currently, all the Node.js Foundation members marked in PRs as just
Member
. So there is no clarity sometimes (especially for new collaborators) if this member (there are 545 now) is also a collaborator (there are 94 now), i.e. if they can run a CI or add labels or land a PR etc. and if help needed.So I've jotted down another little silly bookmarklet to check.
To save it, you can simply select the code (from
javascript: {
up to the last}
) and drag it to the bookmarks panel, then edit the bookmark name.It also can be used as a user script for Tampermonkey, so the check could be run automatically without clicking on the bookmarklet. See user script header example in the first comment of the gist.
To use the bookmarklet, you should be in the 'Conversation' tab of a PR. It can work on other pages, but this was not tested.
The code simply
XMLHttpRequest
s collaborators page, greps usernames and then marks athor links in the PR page according to the collaborators' usernames list — with green (= a user can ran CI etc.) or grey (= a user can't ran CI etc. for now) colors.Feel free to fork and adjust anything)
The text was updated successfully, but these errors were encountered: