Repository navigation
Description
Follow-on to the pilot (#387). Bundles the architectural defers that didn't fit the single-repo scope.
Decision log — 2026-06-14: Multi-repo architecture decided (§1): reusable workflow + thin per-repo caller stubs, callers pinned to the
add-to-project/stablechannel per the org reusable-workflow versioning standard. Not the webhook handler. Execution stays gated on the #414 30-day review (keep / expand / roll back); this issue is now design-complete and shovel-ready. See decision comment.
Why one PR for all of this
These four findings share one architectural answer (a generic 'reconcile content with project' function parameterized by content type and eligibility predicate). Solving them piecemeal would mean rewriting the reconcile machinery once per finding. Bundle them so the underlying mechanism gets designed once.
In scope
1. Multi-repo deployment — ✅ decided
Today the workflow only fires for events in .github. Other repos' qualifying issues/PRs are invisible.
Decision (2026-06-14): reusable workflow + thin per-repo caller stubs. Matches the established dependabot-rebase / auto-rebase / feature-ideation / dev-lead stub pattern; avoids the hosting decision a webhook handler would require.
-
Extract logic into
add-to-project-reusable.yml(hosted in.github); scripts in.github/scripts/add-to-project/stay, threaded via anagent_ref-style input pinned to the same channel. -
The existing
add-to-project.ymlbecomes the thin caller stub for this repo. -
Each adopting repo gets a thin caller pinned once to the moving
stablechannel tag, per ci-standards.md → Reusable workflow versioning:uses: petry-projects/.github/.github/workflows/add-to-project-reusable.yml@add-to-project/stable
Never
@main, never a SHA, never a frozen@vX.Y.Z. -
Release process: merge to
main→ cut immutableadd-to-project/vX.Y.Z→ promotestable(single gated hop today until ring channels exist)..github's own caller is Ring 0 / self-host dogfood. -
Deployment: stubs rolled out via
scripts/deploy-standard-workflows.sh; compliance auditcheck_centralized_workflow_stubsenforces the canonical pin.
Rejected alternative — org-level webhook handler: one deploy, no per-repo stubs, but requires a hosting decision and diverges from the established stub pattern.
2. Issue/PR cleanup-on-label-change (Codex P2 from PR #388 review)
process_issue_or_pr currently only ADDS; it never removes. If an item is added with dev-lead and later receives one of the excluded labels (or has dev-lead removed), the project item stays. Needs:
- Add
unlabeledto issue/PR triggers reconcile_content_with_projectthat mirrorsreconcile_discussion's shape, parameterized by content type + eligibility predicate
3. Hard-coded labels and category
evaluate_noise_gate hard-codes dev-lead + 4 excluded labels. reconcile_discussion hard-codes Ideas. For a second Project to use the same scripts, both must be env-driven. This is the enabler for the reusable extraction in §1 — the gate (dev-lead, the 4 excluded labels, the Ideas category) becomes reusable inputs so each caller passes its own values.
4. Fork-PR maintainer-label gate
pull_request_target gate evaluates the PR author's author_association — so fork PRs from FIRST_TIMER/CONTRIBUTOR authors are skipped even when a maintainer applies dev-lead. Fix: also accept events where the labeler (github.actor on a labeled event) is trusted, OR move trust to head_repository.fork == false.
Out of scope
- New views or fields on the existing project (those are content, not infra)
- Program boards for Compliance / Fleet Monitor — separate decision at 30-day review
Related
- Adopt GitHub Projects: org-level Initiatives pilot #387 — pilot tracking
- this PR validation — Initiatives Project: validation tests + 30-day pilot review #414
- Codex P2 threads on PR feat(workflows): add Initiatives project auto-add workflow #388: PRRT_kwDORyesfc6HD5kS (item removal on excluded), PRRT_kwDORyesfc6HD5kW (label removals), PRRT_kwDORyesfc6Hn464 (maintainer-labeled fork PRs)
Activity
docs(standards): add Initiatives Project operator guide
docs(standards): add Theme field + expanded Initiatives, update for c…
docs(standards): add Initiatives Project operator guide (#417)
docs(standards): add Initiatives Project operator guide (#417)
don-petry commentedon Jun 14, 2026
Architecture decision — §1 Multi-repo deployment
Decided: reusable workflow + thin per-repo caller stubs. Not the org-level webhook handler (avoids a hosting decision and matches the established
dependabot-rebase/auto-rebase/feature-ideation/dev-leadstub pattern).Pinning (per ci-standards.md → Reusable workflow versioning — the
stablechannel): every caller pins the reusable's movingstablechannel tag once —Never
@main, never a SHA, never a frozen@vX.Y.Z. First-party reusable refs are SHA-pin-exempt.Release process: develop/merge to
main→ cut immutableadd-to-project/vX.Y.Zat the merged commit → promotestable(single gated hop today until ring channels exist). The.githubrepo's own caller is Ring 0 / self-host dogfood — it runs the new version first at zero external blast radius beforestablemoves.Knock-on design (keeps "one architectural answer" for all four findings)
add-to-project.ymlbecomes the thin caller stub; all logic moves intoadd-to-project-reusable.yml(scripts in.github/scripts/add-to-project/stay, threaded via anagent_ref-style input pinned to the same channel).dev-lead, the 4 excluded labels, and theIdeascategory become reusableinputs, so each repo's caller passes its own gate. Design this once.reconcile_content_with_project) and §4 (fork-PR maintainer-label gate) ride on the same parameterized reconcile function as planned.Deployment
Per-repo caller stubs deployed via
scripts/deploy-standard-workflows.sh; compliance audit'scheck_centralized_workflow_stubsthen enforces the canonical pin (same as the other Tier-1 stubs).This unblocks §1; remaining
decision neededitems in this issue are resolved. Execution stays gated on the #414 30-day review (keep / expand / roll back) — this just makes "expand" shovel-ready.Generated by Claude Code
feat(add-to-project): reusable workflow + reconcile parity (#415) (#466)
don-petry commentedon Jun 18, 2026
Rollout started early (owner-authorized, ahead of the 2026-07-07 gate)
The implementation PR #466 is merged (main
151347e). Per owner decision, the multi-repo rollout is being kicked off now rather than waiting for the 30-day review gate (#414).Execution is happening from a session with org-wide repo + tag permissions (this session's credentials are scoped to
petry-projects/.githuband can't create the protectedadd-to-project/*tags or write to other repos). Sequenced as:add-to-project/v1.0.0+ movingadd-to-project/stableat151347e(per ci-standards reusable-workflow versioning). Strict prerequisite for step 2.add-to-project.ymltoDEPLOYABLE_WORKFLOWSinscripts/deploy-standard-workflows.sh, thendeploy-standard-workflows.sh --workflow add-to-project.ymlto the 7 other org repos (.github-private,google-app-scripts,bmad-bgreat-suite,broodly,TalkTerm,markets,ContentTwin).Prereqs being confirmed:
petry-projects-plannerapp (ID 3985527) installation must include each target repo; org secretsINITIATIVES_APP_ID/INITIATIVES_APP_PRIVATE_KEYavailable to them. Watchcheck_centralized_workflow_stubs— adding the workflow to the deployable set may flag repos as non-compliant until the deploy lands, so enabler + deploy go together.Verification will follow the #414 smoke tests (dev-lead issue → board; noise-gate exclusion; Ideas discussion → draft). I'll update here with onboarded repos + results as steps land.
Generated by Claude Code
chore(deploy): enable add-to-project.yml stub deployment (#415) (#477)
don-petry commentedon Jun 18, 2026
✅ Multi-repo rollout executed — all 7 consumer repos onboarded
Owner-authorized to start early, ahead of the documented 2026-07-07 review gate (#414).
Step 1 —
stablechannel cut (per ci-standards.md → Reusable workflow versioning)Both tags cut at the #466 merge commit
151347eand verified resolving to it:add-to-project/v1.0.0— immutable release tag (annotated) →151347eadd-to-project/stable— moving production channel →151347e(Phase-1 single-hop promotion: a reusable with only
stabledefined promotes in one gated hop untilnext/ringn channels exist.)Prerequisites verified
petry-projects-planner(App ID3985527) is installed org-wide (repository_selection: all) with exactlyorganization_projects: write,issues: read,pull_requests: read. No missing repos.INITIATIVES_APP_ID/INITIATIVES_APP_PRIVATE_KEYexisted but wereselected-visibility scoped to.githubonly. Extended visibility to all 7 targets.Step 2a — deploy enabler (PR #477, merged)
add-to-project.ymltoDEPLOYABLE_WORKFLOWSinscripts/deploy-standard-workflows.sh.SKIP_OVERRIDESmap so.github-private(normallySKIP_REPOS, self-manages its fleet) receives only this stub..githubstays fully exempt — it hosts its own local-ref self-host caller that a channel-pinned stub must not overwrite.check_centralized_workflow_stubskeys off its own hardcoded list (notDEPLOYABLE_WORKFLOWS) and only validates stubs that already exist;add-to-project.ymlis not inREQUIRED_WORKFLOWSeither — so enabling deployment flags no repo non-compliant. Enabler and deploy landed together regardless.Step 2b — stub deployed to all 7 targets
Verbatim from
standards/workflows/add-to-project.yml(reusable +agent_refpinned toadd-to-project/stable,project_id: PVT_kwDOD2inqs4BZq3-). All 7 verified carrying the stable pin, agent_ref, and project_id:.github-privatebmad-bgreat-suitebroodlyTalkTermgoogle-app-scriptsmarketsContentTwinOperational finding:
deploy-standard-workflows.shpushes directly to each repo's default branch via the Contents API. That works where org-admin bypasses the ruleset, but 3 repos (google-app-scripts,markets,ContentTwin) have branch rulesets that enforce required status checks on direct pushes (HTTP 409 "Required status check … expected") and were not bypassed by the Contents API. I deployed those three via a branch + PR (verbatim template) merged with admin once required checks were green. Worth a follow-up: teach the deploy script a PR mode for ruleset-protected repos rather than relying on direct-push bypass.Smoke tests — see #414. All green;
@add-to-project/stableresolves with nostartup_failure.don-petry commentedon Jun 18, 2026
Follow-up filed for the operational finding noted above: #478 —
deploy-standard-workflows.shshould deploy via PRs (reusing the PR-based primitiveaw-standards-sync.shalready implements) instead of direct Contents-API pushes, which break on ruleset-protected repos and bypass review/CI elsewhere.feat: implement issue #478 — deploy standard workflows via PRs, not d…
feat(add-to-project): rule-driven Initiative/Theme classifier + back-…
feat(add-to-project): reusable workflow + reconcile parity (#415) (#466)
feat(add-to-project): reusable workflow + reconcile parity (#415) (#466)
feat: implement issue #478 — deploy standard workflows via PRs, not d…
feat(add-to-project): reusable workflow + reconcile parity (#415) (#466)
feat(add-to-project): reusable workflow + reconcile parity (#415) (#466)
feat: implement issue #478 — deploy standard workflows via PRs, not d…
feat(add-to-project): reusable workflow + reconcile parity (#415) (#466)
feat: implement issue #478 — deploy standard workflows via PRs, not d…
don-petry commentedon Oct 21, 2026
Closing after the 2026-10-21 backlog triage.
Why: Multi-repo rollout + reconcile parity shipped.
Evidence: PRs #466 #477 #608 #616 merged
Reopen if this still reproduces on main.