Protect main with a ruleset: require CI and drift-check, block force-push

未關閉
#218 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
48/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
github
領域
ci-cd

研究方向

Read the repository’s current protection and ruleset state using the main protection and /rulesets endpoints, then identify the CI matrix and drift-check status checks. Configure the main ruleset with the requested pull request, status-check, force-push, and deletion restrictions, retaining the admin bypass; done when failing-CI PRs cannot merge and direct pushes are rejected.

由索引模型根據 Issue 內容生成。

描述

ci effort: small impact: medium priority: medium release

Why it matters

Every merge to main triggers release.yml, which tags and publishes to npm and the MCP Registry. main has no protection, so a direct push or a merge with red CI ships to users. #190 covers the release workflow not waiting for CI, and #191 covers action hardening; neither covers repository rules.

Evidence

  • gh api repos/TMHSDigital/screencast-mcp/branches/main/protection returns 404 (not protected).
  • /rulesets is empty.

Suggested approach

Add a ruleset on main:

  • require pull requests
  • require the CI matrix (Ubuntu and Windows) and drift-check to pass
  • block force-pushes and deletion
  • optionally require linear history

Allow an admin bypass for emergencies.

Done when

  • A PR with failing CI cannot be merged.
  • A direct push to main is rejected.
主要語言
TypeScript
星號
1
分支
4
平均合併
14 小時 8 分鐘
30 天內合併 PR
48

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TMHSDigital/screencast-mcp 的其他 Issue

查看 TMHSDigital/screencast-mcp 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。