Skip to content

docs: expand CentralRepoOps with agentic factory pattern#38462

Closed
Copilot wants to merge 9 commits into
mainfrom
copilot/expand-documentation-central-repo-ops
Closed

docs: expand CentralRepoOps with agentic factory pattern#38462
Copilot wants to merge 9 commits into
mainfrom
copilot/expand-documentation-central-repo-ops

Conversation

Copilot AI commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

CentralRepoOps covered control-plane dispatch and tracker aggregation but omitted the third model: the central repo as a self-contained packaging envelope for an org's entire agentic suite.

Changes

  • patterns/central-repo-ops.md — adds "The Central Repo as an Agentic Factory" section: a single repo that holds all workflows, gets dropped into a new org, and starts running after secrets are configured. No template structure, no manifest requirement — just the concept and framing.
  • Related docs — adds link to Sharing Workflows in the Organization.
  • Lock files — merged main and recompiled; 13 lock files updated with threat-detection maxAiCredits runtime-override from main.

Copilot AI and others added 2 commits June 10, 2026 23:54
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title docs: expand central-repo-ops with agentic factory pattern docs: expand CentralRepoOps with agentic factory pattern Jun 10, 2026
Copilot AI requested a review from pelikhan June 10, 2026 23:56
@pelikhan

Copy link
Copy Markdown
Collaborator

@copilot The central repo package doesn’t require a manifest. It should be a self-contained system with a README that serves as a manual for how to activate it. It can use a manifest, but it isn’t mandatory.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot AI commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

@copilot The central repo package doesn’t require a manifest. It should be a self-contained system with a README that serves as a manual for how to activate it. It can use a manifest, but it isn’t...

Fixed in the latest commit. The template structure now leads with README.md as the activation manual and the workflows as the core of the factory. aw.yml is shown last in the directory tree, annotated as optional, and its section is titled "Optional: Distribution via aw.yml" with the framing that it can be added to enable gh aw add installs — but the factory is fully operational without it.

@dsyme

dsyme commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

The OG of this page was wildly complicated, out of control.

Comment on lines +110 to +113
├── shared/
│ ├── mcp-config.md # shared MCP server definitions
│ └── safety-policy.md # shared safe-outputs policies
└── aw.yml # optional: enables gh aw add installs

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot a factory does not need to be reusable, remove these files or move shares under .github/workflows/shared

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved under .github/workflows/shared/ in the latest commit. The top-level shared/ directory is gone.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI requested a review from pelikhan June 11, 2026 00:43
@pelikhan

Copy link
Copy Markdown
Collaborator

OG?

Comment on lines +141 to +168
### Optional: Distribution via `aw.yml`

Adding an `aw.yml` manifest is optional but enables teams to install individual workflows from the factory using `gh aw add` rather than cloning or forking the whole repository:

```yaml
name: Acme Org Agentic Factory
emoji: 🏭
description: Standard agentic workflows for Acme org repositories
min-version: v0.40.0
includes:
- .github/workflows/rollout.md
- .github/workflows/triage.md
- .github/workflows/quality-monitor.md
- .github/workflows/dependabot.md
- .github/workflows/shared/mcp-config.md
- .github/workflows/shared/safety-policy.md
```

A consuming repository installs a specific workflow:

```bash
gh aw add acme-org/agentic-workflows/triage@v1.0.0
```

Pin consumers to a release tag for stability. As the factory evolves, run `gh aw update` in consuming repositories to pull in upstream changes with a 3-way merge that preserves local edits.

See [Sharing Workflows in the Organization](/gh-aw/practices/sharing-workflows/) for versioning strategy, governance recommendations, and the recommended enterprise pattern for a central `agentic-workflows` repository.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot remove this section or aw.yml in this section

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the section entirely in the latest commit — along with aw.yml from the directory tree and the related-docs link.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI requested a review from pelikhan June 11, 2026 00:59
@github-actions github-actions Bot mentioned this pull request Jun 11, 2026
Comment on lines +97 to +138
### Template Repository Structure

A factory repository is self-contained: the `README.md` is the activation manual, and the workflows under `.github/workflows/` are ready to run once secrets are configured.

```
agentic-workflows/
├── README.md # activation manual (secrets, setup, verify)
└── .github/
└── workflows/
├── rollout.md # org-wide rollout orchestrator
├── triage.md # cross-repo issue triage
├── quality-monitor.md # code quality monitoring
├── dependabot.md # dependency management
└── shared/
├── mcp-config.md # shared MCP server definitions
└── safety-policy.md # shared safe-outputs policies
```

Mark the repository as a [GitHub template repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-template-repository) so anyone in the organization can instantiate a personal copy in one click without carrying over existing workflow runs or secrets.

### Secrets Checklist

The `README.md` should include a complete secrets checklist so anyone instantiating the factory knows exactly what to configure. A typical factory needs:

| Secret | Purpose |
| ------ | ------- |
| `ANTHROPIC_API_KEY` / `GEMINI_API_KEY` | AI engine for agent runs |
| `GH_AW_READ_ORG_TOKEN` | Read org metadata and repository list |
| `GH_AW_CROSS_REPO_PAT` | Write safe outputs to target repositories |
| `ORG_REPO_CHECKOUT_TOKEN` | Check out target repositories for workers |

> [!TIP]
> Use a GitHub App rather than PATs for cross-repository tokens where possible. GitHub Apps provide automatic token rotation and fine-grained per-repository scoping. See [Authentication](/gh-aw/reference/auth/) for setup.

### Activation: Drop In, Configure, Run

1. **Instantiate** — Create a new repository from the factory template in the target org (or fork it for independent configuration).
2. **Configure** — Add the required secrets to the new repository's **Settings → Secrets → Actions**.
3. **Enable Actions** — Confirm GitHub Actions is enabled for the repository and that scheduled workflows are not paused.
4. **Verify** — Trigger a `workflow_dispatch` on one workflow to confirm end-to-end connectivity before the first scheduled run fires.

Once secrets are in place, all scheduled workflows activate automatically and the factory is producing.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot remove this section

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done — the Template Repository Structure, Secrets Checklist, and Activation subsections have been removed. The factory section now just carries the two introductory paragraphs describing the concept.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI requested a review from pelikhan June 11, 2026 01:39
@pelikhan

Copy link
Copy Markdown
Collaborator

@copilot run pr-finisher skill

@github-actions

Copy link
Copy Markdown
Contributor

Hey @copilot-swe-agent 👋 — great addition to the CentralRepoOps docs! The "agentic factory" metaphor is a genuinely useful framing for the packaging-envelope deployment model and the new section reads cleanly.

One thing to tighten up before this is ready:

  • Split the lock-file changes — the diff includes schema additions to 11 .lock.yml files (adding a branch field to push_to_pull_request_branch) and a label rename in agent-factory-status.mdx, neither of which are mentioned in the PR description. These appear to be unrelated changes bundled into a docs PR. Ideally the lock-file schema update ships as its own focused PR so reviewers can evaluate each concern independently.

If you'd like a hand, you can assign this prompt to your coding agent:

The PR titled "docs: expand CentralRepoOps with agentic factory pattern" (github/gh-aw#38462) bundles two unrelated changes:
1. Docs-only change: docs/src/content/docs/patterns/central-repo-ops.md (new "Agentic Factory" section + Related Docs link) and docs/src/content/docs/agent-factory-status.mdx (label rename).
2. Schema change: 11 .github/workflows/*.lock.yml files each adding a `branch` field definition under `push_to_pull_request_branch`.

Please split these into two separate PRs:
- PR A: docs-only changes (central-repo-ops.md + agent-factory-status.mdx)
- PR B: lock-file schema additions across the 11 workflow lock files

Make sure each PR has a description that matches its actual contents.

Generated by ✅ Contribution Check · 392.9 AIC · ⌖ 12.9 AIC · ⊞ 24.7K ·

@pelikhan

Copy link
Copy Markdown
Collaborator

@copilot merge main and recompile

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Copilot AI commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

Hey @copilot-swe-agent 👋 — great addition to the CentralRepoOps docs! The "agentic factory" metaphor is a genuinely useful framing for the packaging-envelope deployment model and the new sectio...

The concern about bundled lock-file changes has been addressed. After merging main (which canonically owns the branch-field and maxAiCredits additions) and running make recompile, the lock files are now fully up to date with main and no longer represent a separate, unbundled schema change in this PR. The only diff against main in this branch is now the docs addition to central-repo-ops.md.

Copilot AI commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

@copilot merge main and recompile

Done — merged main into the branch and ran make recompile. 13 lock files were updated with the threat-detection maxAiCredits runtime-override from main. The only diff against main is now the docs addition to central-repo-ops.md.

@pelikhan pelikhan closed this Jun 11, 2026
@github-actions github-actions Bot deleted the copilot/expand-documentation-central-repo-ops branch June 19, 2026 03:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants