Creating pipelines zip archive in docs CI on every push to a PR branch
还没有人认领这个 Issue。
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 88/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 冷清
- 技术栈
- github-actions
- 领域
- ci-cd, documentation
调研方向
从 .github/workflows/httomo_docs.yml 开始，检查第 43-45 行和第 56-60 行的 artifact 创建，以及第 51 行附近的 docs 上传条件。调整 workflow 条件，使 pipelines artifact 仅在 releases 中创建，然后验证推送到 PR 分支时不会上传它，而 release 运行仍会上传它。
由索引模型根据 Issue 内容生成。
描述
I noticed that there's an artifact getting uploaded as part of the docs build CI even if the CI wasn't triggered by a tag push:
The artifact isn't very big (taken from https://github.com/DiamondLightSource/httomo/actions/runs/24771337928/job/72478300291?pr=708):
With the provided path, there will be 1 file uploaded
Artifact name is valid!
Root directory input is valid!
Beginning upload of artifact content to blob storage
Uploaded bytes 16937
Finished uploading artifact content to blob storage!
SHA256 digest of uploaded artifact zip is 5e9dd090dcaad7c024f063b92dcd1c1b6e945ce80a57d2491132ba2461fd364a
Finalizing artifact upload
Artifact full_pipelines-artifact.zip successfully finalized. Artifact ID 6575004505
Artifact full_pipelines-artifact has been successfully uploaded! Final size is 16937 bytes. Artifact ID is 6575004505
Artifact download URL: https://github.com/DiamondLightSource/httomo/actions/runs/24771337928/artifacts/6575004505
but if this happens every time a push is done to a PR branch then this could accumulate, and I imagine it'd accumulate somewhere associated with the repo and it'll eventually reach a storage limit of some kind.
We probably want to only create this artifact for releases, which would be equivalent to something like the following condition used for the docs upload, just without the main part: https://github.com/DiamondLightSource/httomo/blob/899a43da8c63a1431d0804dcb48773be08b46710/.github/workflows/httomo_docs.yml#L51
- 主要语言
- Python
- 星标
- 10
- 派生
- 5
- 平均合并
- 6 分钟
- 30 天内合并 PR
- 1
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DiamondLightSource/httomo 的其他 Issue
-
framework minor
难度 2/5 1-3 小时 新手友好度 72/100
DiamondLightSource/httomo#699 ·
-
documentation question
难度 2/5 1-3 小时 新手友好度 68/100
DiamondLightSource/httomo#697 ·
-
难度 1/5 1 小时以内 新手友好度 72/100
DiamondLightSource/httomo#609 ·
-
难度 2/5 1-3 小时 新手友好度 62/100
DiamondLightSource/httomo#607 ·
-
documentation
难度 2/5 1-3 小时 新手友好度 68/100
DiamondLightSource/httomo#585 ·
查看 DiamondLightSource/httomo 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
GoogleCloudPlatform/gce-rescue#195 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
intake mcp-intake needs-ac needs-human-review priority:medium
难度 2/5 1-3 小时 新手友好度 67/100
Ikalus1988/MisakaNet#3848 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 75/100
521xueweihan/HelloGitHub#4105 ·
-
bug size:XS
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复