Provide an auto-publish GitHub action for Spago users
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
The existing behavior is in scripts/src/DailyImporter.purs; start by reading that importer and the proposed SemVer-tag trigger. Done means a released GitHub Action that publishes tagged packages to the registry and makes failures visible to authors, while addressing the described repository layouts.
由索引模型根據 Issue 內容生成。
描述
Today we provide a DailyImporter script which will attempt to publish any newly-discovered tags on existing registered repos from GitHub. We do this because there are packages — such as all of purescript as an organization — which haven't switched to Spago yet and therefore don't publish to the registry.
This has a number of issues:
- If a package version has a problem which prevents it from being published, the author has no idea and the version simply doesn't get registered.
- It only supports GitHub packages with version-like tags, which goes against the registry goals to be agnostic to where you store your code and to allow for monorepo/polyrepo setups
However, it's very convenient. So instead I propose we write and release a GitHub action which does the same thing the importer does — when you push a new SemVer tag it will auto-publish to the registry — that authors can install on their repositories.
It would produce the same effect but:
- the author is aware when there is an issue
- we could potentially make it flexible to detect polyrepo setups and use the
subdirkey to publish within a polyrepo without requiring a top level tag (could be triggered by something like contents of a commit message)
The daily import can coexist with this action easily as it doesn't republish already-published package versions. Even if there were a bug and it tried then the registry would reject the job.
- 主要語言
- PureScript
- 星號
- 95
- 分支
- 79
- 平均合併
- 16 小時 13 分鐘
- 30 天內合併 PR
- 14
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
purescript/registry-dev 的其他 Issue
-
難度 5/5 一週以上 新手友好度 22/100
purescript/registry-dev#804 · 9 則留言 ·
維護者通常 1 天內回覆
-
A failed publish job permanently blocks retrying the same package version可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 4/5 3-5 天 新手友好度 48/100
purescript/registry-dev#793 · 5 則留言 ·
維護者通常 1 天內回覆
-
Implement search and versioned Prim docs for the new Pursuit可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉pursuit
purescript/registry-dev#790 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Migrate Pursuit application to the monorepo可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉pursuit
purescript/registry-dev#789 · 1 則留言 · 1 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Complete support for monorepos / subdir key and non-GitHub locations可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉
purescript/registry-dev#750 · 1 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 purescript/registry-dev 的全部 Issue
相似的 Issue
-
could-have reliability
難度 1/5 1 小時以內 新手友好度 88/100
-
enhancement
難度 2/5 1-3 小時 新手友好度 62/100
alunduil/renovate-config#61 ·
維護者通常 1 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 62/100
alunduil/projects-v2-sync#159 ·
維護者通常 1 天內回覆
-
area/apigee type/bug
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
good first issue
難度 2/5 1-3 小時 新手友好度 78/100
dataforgoodfr/mediterranean-rescue#91 ·
維護者通常 1 天內回覆