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 于 109 天前认领，目前没有进行中的 PR。 未关闭pursuit
purescript/registry-dev#790 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Migrate Pursuit application to the monorepo可能重新可做 @thomashoneyman 于 109 天前认领，目前没有进行中的 PR。 未关闭pursuit
purescript/registry-dev#789 · 1 条评论 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
-
Complete support for monorepos / subdir key and non-GitHub locations可能重新可做 @thomashoneyman 于 109 天前认领，目前没有进行中的 PR。 未关闭
purescript/registry-dev#750 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
查看 purescript/registry-dev 的全部 Issue
相似的 Issue
-
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 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
cpp-best-practices/project_validator#267 ·
维护者通常 1 天内回复
-
deploy tests
难度 2/5 1-3 小时 新手友好度 76/100
damodharg6/payledger#6 ·
-
难度 2/5 1-3 小时 新手友好度 70/100