Route v13 API-docs CI and publication to website branch v13
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 40/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- github-actions
- 領域
- ci-cd
研究方向
Start with the api-docs job in .github/workflows/ci.yml and the publish job in .github/workflows/publish.yml, and find where each checks out the website's default branch. Add a step that derives the compiler major from the version, including prereleases, and maps 12 to master and 13 to v13. Then confirm that the artifact lands in data/api and that publishing commits to the chosen branch. Done means both workflows select the branch correctly for stable and alpha versions, and the v12 path is unchanged. Website #1433 must land first.
由索引模型根據 Issue 內容生成。
描述
Compiler master generates v13 API snapshots, but both the API-docs CI check and release publication check out the website's default branch. Website master selects v12 data, so building it with a new v13 artifact does not validate v13 API pages, and publishing there does not update the website's v13 branch.
Target branch: compiler master (v13). This changes workflow routing, not compiler language behavior.
- In
.github/workflows/ci.yml, make theapi-docsjob check out the matching website branch before downloading and building the generated artifact. - In
.github/workflows/publish.yml, use the same branch mapping for the website checkout, build, and API-data commit/push. - Map compiler major 12 to website
master, and compiler major 13 to websitev13. Derive the major from the compiler/release version, including prereleases. - Download artifacts into repository-root
data/api, and require a successful build of the matching website before publishing its API-data changes.
Acceptance: v13 CI builds website branch v13 with the incoming v13 snapshot; v13 release publication commits that snapshot to v13 and triggers the appropriate website deployment. Verify branch selection for stable and alpha versions, and preserve the v12 maintenance publication path to website master.
Prerequisite: website #1433 must land first so the v13 website consumes and validates the published data. Confirm the v13 website deployment trigger as part of the coordinated rollout.
Related: website #1391 and website PR #1432.
- 主要語言
- OCaml
- 星號
- 7.5k
- 分支
- 484
- 平均合併
- 1 天 1 小時
- 30 天內合併 PR
- 120
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
rescript-lang/rescript 的其他 Issue
-
難度 5/5 一週以上 新手友好度 25/100
rescript-lang/rescript#8833 · 1 個 reaction ·
維護者通常 1 天內回覆
-
rewatch watch on Linux stops watching a source folder when an overlapping recursive source folder is removed from rescript.json可能已有人在做 @cknitt 於 2 天前認領。 未關閉
難度 4/5 1-2 天 新手友好度 35/100
rescript-lang/rescript#8825 ·
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 35/100
rescript-lang/rescript#8806 ·
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 35/100
rescript-lang/rescript#8798 ·
維護者通常 1 天內回覆
-
難度 3/5 半天 新手友好度 58/100
rescript-lang/rescript#8757 ·
維護者通常 1 天內回覆
查看 rescript-lang/rescript 的全部 Issue
相似的 Issue
-
area: ci complexity: trivial impact: low
難度 1/5 1 小時以內 新手友好度 72/100
ueberdosis/tiptap#8521 ·
維護者通常 1 天內回覆
-
internal os specific
難度 2/5 1-3 小時 新手友好度 65/100
frostney/GocciaScript#1688 ·
維護者通常 1 天內回覆
-
benchmark: `make setup` fails because audit-exporter builds with Go 1.25.0 while go.mod requires 1.26.0可能已有人在做 @xsvm 今天認領。 未關閉
難度 1/5 1 小時以內 新手友好度 84/100
volcano-sh/volcano#6097 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 62/100
aristanetworks/avd#7579 ·
維護者通常 1 天內回覆
-
[oblt-aw][autodoc] Update PR Actions Detective E2E prerequisites and fix dashboard-format table typo未關閉documentation
難度 2/5 1-3 小時 新手友好度 75/100
elastic/oblt-aw#2382 · 1 則留言 ·
維護者通常 1 天內回覆