blocklist import/export
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 25/100
- Issue 類型
- 功能
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- github-actions, javascript
研究方向
先檢視 cutenode/action-import-blocklist，以及為 pkgjs、nodejs-private 或 nodejs 提議的 .github 儲存庫與工作流程。在實作之前解決 ownership、PAT admin:org、排程和 username-logging 相關問題。當三個組織之間透過一個已達成共識、由專案擁有的工作流程同步 blocklist 時，即表示完成。
由索引模型根據 Issue 內容生成。
描述
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?
- 主要語言
- JavaScript
- 星號
- 202
- 分支
- 183
- 平均合併
- 13 天 12 小時
- 30 天內合併 PR
- 2
環境準備
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
nodejs/admin 的其他 Issue
-
難度 1/5 1 小時以內 新手友好度 90/100
-
tsc-agenda
難度 5/5 一週以上 新手友好度 30/100
-
難度 5/5 一週以上 新手友好度 35/100
-
難度 5/5 一週以上 新手友好度 35/100
-
難度 5/5 一週以上 新手友好度 30/100
相似的 Issue
-
Design only Leadership Survey SLFS
難度 2/5 1-3 小時 新手友好度 70/100
bcgov/digital-journeys#2293 ·
-
Toolkit
難度 2/5 1-3 小時 新手友好度 88/100
維護者通常 1 天內回覆
-
API Bug
難度 2/5 1-3 小時 新手友好度 78/100
ProjectSidewalk/SidewalkWebpage#5556 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
jessepollak/home#1454 ·
維護者通常 1 天內回覆
-
Mend: dependency security vulnerability untriaged
難度 2/5 1-3 小時 新手友好度 64/100
opensearch-project/OpenSearch-Dashboards#12822 ·
維護者通常 1 天內回覆