Configure one-time repository settings: Pages source, private vulnerability reporting and branch protection

オープン
#19 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
20/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github, github-actions, typescript

調査の方向性

Read README.md's Deployment section, SECURITY.md, CONTRIBUTING.md, and the four workflows under .github/workflows; inspect .github/labels.json and .github/milestones.json for the sync requirements. Configure the repository settings and validate CI, Pages, vulnerability reporting, branch protection, and the release workflow as listed in the acceptance criteria. It is done when every listed check and repository setting succeeds.

索引モデルが issue の本文から書いたものです。

説明

area: infra priority: high type: chore

Context

Some settings cannot be configured from files in the repository. Without the Pages source, pages.yml cannot deploy; without private vulnerability reporting, the reporting path in SECURITY.md and the "Report a security vulnerability" link in the issue chooser lead nowhere; without branch protection, the review rule in CONTRIBUTING.md (one approval and green CI) is not enforced. The workflow hardening of v0.1 (SHA pins, read-only tokens) was checked only by parsing the YAML, so the first real runs of CI, Pages and Release need checking too.

Scope

A maintainer with admin rights:

  1. Settings, Pages, Build and deployment: Source = GitHub Actions.
  2. Settings, Code security: Private vulnerability reporting = enabled.
  3. A branch protection rule or ruleset for main: pull requests required, one approving review, the CI checks (build, end-to-end tests, prompt kit) required.
  4. On the v0.1 pull request: check that the three CI jobs pass on GitHub's runners.
  5. After the merge: run the Repo sync workflow if labels or milestones are missing, check the first Pages deployment, and push a pre-release tag (for example v0.1.0-rc.1) to test the release workflow.

Acceptance criteria

  • CI passes on GitHub for the v0.1 pull request (build, end-to-end tests, prompt kit).
  • The Pages workflow on main succeeds and https://nullthrone.github.io/lexvm/ serves the player.
  • https://nullthrone.github.io/lexvm/lexvm-offline.html downloads the single-file build.
  • A pre-release tag runs release.yml and publishes lexvm-offline.html, the compiled packs and SHA256SUMS.txt.
  • Private vulnerability reporting is enabled; the security link in the issue chooser opens the advisory form.
  • A direct push to main is refused, and a pull request cannot be merged with failing CI or without an approval.
  • All labels from .github/labels.json and milestones from .github/milestones.json exist.

References

  • README.md (Deployment)
  • SECURITY.md
  • CONTRIBUTING.md (Review process)
  • .github/workflows/ci.yml
  • .github/workflows/pages.yml
  • .github/workflows/release.yml
  • .github/workflows/repo-sync.yml
  • .github/ISSUE_TEMPLATE/config.yml
  • docs/adr/0006-offline-first-pwa-on-github-pages.md
主要言語
TypeScript
スター
0
フォーク
0
平均マージ
1時間 24分
マージ済み PR(30日)
5

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nullthrone/lexvm のほかの issue

nullthrone/lexvm の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。