BuildHelpers revival
Tracking issue for bringing BuildHelpers from status-incoming to status-active.
Steward: @tablackburn. Repo: https://github.com/PowerShellOrg/BuildHelpers.
Each phase is a sub-issue below. Phases overlap; pace to the state of the repo, not the
week numbers. Reference material (comment templates, decision tree, YAML, release steps) is in
the Revival Playbook.
Baseline (captured at transfer)
| Metric |
Value |
| Transfer date |
between 2026-08-22 and 2026-09-04 |
| Last commit |
2023-08-11 |
| Open issues |
30 |
| Open PRs |
11 |
| Stars / forks |
221 / 48 |
| Existing CI |
AppVeyor |
| Last PSGallery release |
v2.0.16 (2020-12-18) |
| PSGallery downloads |
fill in |
These numbers go in the first release announcement. (Corrected by hand to transfer-time values; the generator ran after the caller workflow commit and six interim issues.)
Working with an AI assistant
Point it at the playbook and this issue. It drafts; you post. Comments on other people's
issues, PR closes, and merges are yours to click.
BuildHelpers revival
Tracking issue for bringing BuildHelpers from
status-incomingtostatus-active.Steward: @tablackburn. Repo: https://github.com/PowerShellOrg/BuildHelpers.
Each phase is a sub-issue below. Phases overlap; pace to the state of the repo, not the
week numbers. Reference material (comment templates, decision tree, YAML, release steps) is in
the Revival Playbook.
Baseline (captured at transfer)
These numbers go in the first release announcement. (Corrected by hand to transfer-time values; the generator ran after the caller workflow commit and six interim issues.)
Working with an AI assistant
Point it at the playbook and this issue. It drafts; you post. Comments on other people's
issues, PR closes, and merges are yours to click.