Move the deploy workflow's routing and sentinel steps into tested scripts
维护者通常 2 天内回复
已经有一个关联 PR 被合并了。
- #1004 来自 @anth-volk —— 已合并
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 1/100
调研方向
Start with .github/workflows/simulation-deploy.reusable.yml and the seven named steps, then inspect rules/baselines/ci-multiline-run.txt and the tests that read shell from the workflow YAML. Move each block into a tested script under .github/scripts/, update the tests to run those scripts, and remove the seven baseline entries. Done when all seven steps keep identical behavior and their tests pass.
由索引模型根据 Issue 内容生成。
描述
Phase 1 step 1.7 of the rules work, follow-up to #763: the seven multi-line run: blocks that #743 and #744 added to .github/workflows/simulation-deploy.reusable.yml move into tested scripts under .github/scripts/, each called from a single-command step, with identical behaviour.
The seven steps:
update_routing: Plan the routing change, Record the unfinished routing publication, Publish the planned routingsentinel_expected: Check the sentinel names this deployment's bundleintegration: Check the deployed stack reproduces the sentinel numberspromote_entrypoint: Verify the stable service reproduces the sentinel numbersfinalize_routing: Finalize the routing publication
#763 left them in rules/baselines/ci-multiline-run.txt (rule sim.ci.multiline-run-is-script) because their tests read the steps' shell from the workflow YAML. Those tests are rewritten to run the scripts, and the seven baseline entries are removed. The six blocks in simulation-rollback.yml follow in a separate pull request.
- 主要语言
- Python
- 星标
- 1
- 派生
- 1
- 平均合并
- 2 天 48 分钟
- 30 天内合并 PR
- 87
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-sim-api 的其他 Issue
-
Update policyengine to 6.7.3可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 2/5 半天 新手友好度 70/100
PolicyEngine/policyengine-sim-api#823 ·
维护者通常 2 天内回复
-
Integration tests fail due to missing UV virtual environment setup可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
PolicyEngine/policyengine-sim-api#314 ·
维护者通常 2 天内回复
-
Update policyengine to 6.15.0可能已有人在做 @policyengine 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 1/100
PolicyEngine/policyengine-sim-api#1014 ·
维护者通常 2 天内回复
-
Move the simulation executor to policyengine.py 6.14.0 and keep accepting US 2022 and 2023可能已有人在做 @anth-volk 于 1 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 25/100
PolicyEngine/policyengine-sim-api#1012 ·
维护者通常 2 天内回复
-
Update policyengine to 6.14.0可能已有人在做 @policyengine 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 58/100
PolicyEngine/policyengine-sim-api#1010 ·
维护者通常 2 天内回复
查看 PolicyEngine/policyengine-sim-api 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 64/100
FinanceFlash/unvibecode#577 · 1 条评论 ·
维护者通常 1 天内回复
-
area/test type/bug
难度 2/5 1-3 小时 新手友好度 76/100
Clodmony/starship-coop#70 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
punitarani/fli#270 ·
-
🐛 Bug 🔔 Pending processing
难度 2/5 1-3 小时 新手友好度 67/100
jumpserver/jumpserver#17980 ·
维护者通常 1 天内回复
-
community enhancement good first issue
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复