Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Certify Microcosm UK national cut a133f37a for the Autumn Budget

未关闭
#714 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@MaxGhenis 已经在做这个了。

开始于 2026年10月24日。

  • #715 来自 @MaxGhenis —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
python
领域
data, testing-qa

调研方向

Start with docs/engineering/skills/data-certification.md and the referenced decisions d1682 and d1344 to understand the same-line re-cut exception. Use the specified cut, policyengine-uk==2.147.2, core 3.33.3, build 829c1bc26, and --drop-regional-release; the evidence must cover every listed gate, snapshots, attribution, and strict check. Done also requires the scorecard replay to become available and pass.

由索引模型根据 Issue 内容生成。

描述

Certify Saturday's Microcosm UK national cut microcosm-uk-2024-25-national-20261023T075039Z-a133f37a for the Autumn Budget (28 October), on policyengine-uk==2.147.2 and core 3.33.3.

This is the same-line re-cut exception that docs/engineering/skills/data-certification.md records (the Budget coordinator's 23 October decision under d1682 and d1344):

  • the data stays on the microcosm-uk-2024-25-national line;
  • the model is pinned to the cut's build-time version (Microcosm build 829c1bc26, on main via PolicyEngine/microcosm#1338);
  • certification is national-only (--drop-regional-release), stacked on #704 (budget-local-data-manifest). Constituency and local-authority outputs are absent until Monday's cut.

Evidence package owed in the PR:

  • the release-cut gates;
  • the UC floor;
  • the snapshots;
  • the #574 reform contract and the Budget-inputs gates on the exact cut;
  • the strict check;
  • the same-line 2×2 attribution against 6cba5d71 on pe-uk 2.132.6, for FY2026-27 to FY2030-31.

Scorecard replay is recorded as unavailable until the Microcosm replay fix lands; unavailable is not a pass.

María Juaristi (juaristi22) can override the routing decision.

🤖 Generated with Claude Code

主要语言
Python
星标
8
派生
10
平均合并
1 天 2 小时
30 天内合并 PR
51

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

PolicyEngine/policyengine.py 的其他 Issue

查看 PolicyEngine/policyengine.py 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。