Skip to content

Phase 4: Cross-org deployment of gh-aw workflows #235

Closed

Description

@don-petry

Context

Part of the GitHub Agentic Workflows rollout — Discussion #228.

Depends on: #234 (Phase 3 — Stale Manager + Release Notes must be stable first)

Goal

Make the gh-aw workflows available across all petry-projects repos, not just .github-private. The deployment strategy is decided here based on Phase 3 stability.

Decision gate

At the start of this phase, evaluate workflow stability from Phases 1–3:

  • If all three workflows have been live for 5+ days with no incidents → use the gh-aw shared workflow packaging approach (gh aw package) to publish from .github-private and reference from other repos.
  • If any workflow is still being iterated → extend the existing org dispatch pattern (same architecture as current pr-review mention trigger) to keep workflows centralized.

Document the decision in the PR description.

Tasks (shared workflow path)

  • Run gh aw package in .github-private to generate the shared workflow bundle
  • Add the package reference to .github (public org config repo) so all repos can consume it
  • Verify Issue Triage fires correctly in at least two non-infrastructure repos: ContentTwin and one other
  • Verify CI Failure Analyst fires on a real failure in a non-infrastructure repo

Tasks (org dispatch path)

  • Extend .github/workflows/ dispatcher to route gh-aw workflow triggers from org repos back to .github-private
  • Test in ContentTwin and one other repo
  • Document the routing architecture in docs/aw/cross-org-deployment.md

Acceptance Criteria

  • Deployment strategy decision documented
  • Issue Triage and CI Failure Analyst verified firing in 2+ non-infrastructure repos
  • No regressions in .github-private workflows
  • Deployment approach documented in docs/aw/cross-org-deployment.md
  • All changes via PR

Activity

  1. don-petry commented on May 20, 2026

    @don-petry
    CollaboratorAuthor

    @dev-lead please implement this issue as a stacked PR on top of PR #299. Base your branch on dev-lead/issue-234-20260520-0234 (Phase 3's branch), not on main.

  2. don-petry commented on May 20, 2026

    @don-petry
    CollaboratorAuthor

    Phase 4 complete — PR #302 fully passing. Chaining to Phase 5 (#236) — the final phase.

  3. added a commit that references this issue on May 20, 2026
  4. added 8 commits that reference this issue on Jun 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dev-leadFor dev-lead agent pickup

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions