blocklist import/export
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, javascript
Research direction
Start by reviewing cutenode/action-import-blocklist and the proposed .github repositories and workflows for pkgjs, nodejs-private, or nodejs. Resolve the ownership, PAT admin:org, scheduling, and username-logging questions before implementing. Done means blocklists sync between the three organizations through an agreed project-owned workflow.
Written by the indexing model from the issue text.
Description
per the recent discussion around the moderation team and importing/exporting the blocklist across our three orgs (nodejs, pkgjs, and nodejs-private), I went ahead and built out a GitHub Action that allows us to import blocklists from one organization to another organization. In practice, this means that if someone is blocked in the nodejs org, that block can be imported to the other organizations automatically (presumably on a cron or manual run of the Action, rather than being directly triggered by the block event).
You can find the code in cutenode/action-import-blocklist. Implementing it requires a PAT from an account (presumably, in our case, the Node.js bot account) that has the full admin:org permissions, which is required by the GitHub API.
@nodejs/tsc @nodejs/actions want to get feedback on this. My proposal:
- implement syncing to
pkgjsandnodejs-privateby setting up.githubrepositories in both and adding workflows. I'm happy to help with this, but it's pretty trivial. - alternatively, implement syncing by setting up a
.githubrepo in thenodejsorg, allowing us to have control within the project of where our blocklist is being exported to and not providingadmin:orgtokens to those orgs (pkgjs is notably more permissive).
questions I have:
- currently, the Action uses
console.log()to output what's happening. This does include usernames. Is this okay, or would we want to omit those? - I'd prefer to move the action to a project-owned organization. Does this belong under
nodejsor underpkgjs?
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 13d 12h
- Merged PRs (30d)
- 2
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/admin
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 78/100
jaegertracing/jaeger-ui#4512 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#3857 ·
Maintainers usually reply within 2 days
-
area-clientside-dartpad
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
quarkusio/extensions#3432 ·
Maintainers usually reply within 1 day