From cb83aa711fc15cb039d0de0d85f3ef99ea88dc62 Mon Sep 17 00:00:00 2001 From: gh-aw bot Date: Sat, 7 Mar 2026 00:08:46 +0000 Subject: [PATCH 1/2] docs: unbloat SideRepoOps page - condense bullets into prose - Removed 5-bullet "Key Benefits" list, integrated into concise prose - Removed redundant explanatory sentence after ASCII architecture diagram - Merged "Related Patterns" and "Related Documentation" sections into a single "Related" section with inline links Reduces from 408 to 388 lines; eliminates all 14 bullet points (100% reduction in bullet count). Co-Authored-By: Claude Sonnet 4.6 --- .../content/docs/patterns/side-repo-ops.mdx | 28 +++---------------- 1 file changed, 4 insertions(+), 24 deletions(-) diff --git a/docs/src/content/docs/patterns/side-repo-ops.mdx b/docs/src/content/docs/patterns/side-repo-ops.mdx index f653dadebc5..863f7606463 100644 --- a/docs/src/content/docs/patterns/side-repo-ops.mdx +++ b/docs/src/content/docs/patterns/side-repo-ops.mdx @@ -11,16 +11,7 @@ SideRepoOps is a development pattern where you run agentic workflows from a sepa ## When to Use SideRepoOps -**Getting Started**: SideRepoOps is ideal when you're new to agentic workflows and want a low-risk way to experiment. You can test automation without adding files to your main repository or worrying about breaking existing workflows. - -**Key Benefits**: -- **Zero friction** - No changes needed to your main repository -- **Clean separation** - AI-generated issues stay separate from organic development -- **Private workflows** - Store sensitive automation logic in a private repository -- **Safe experimentation** - Perfect for testing and learning before production deployment -- **Centralized automation** - Manage workflows for repositories you don't directly control - -Use SideRepoOps for workflow experimentation, creating a centralized automation hub, or managing automation for multiple repositories. +SideRepoOps is ideal when you're new to agentic workflows and want a low-risk way to experiment — no changes needed to your main repository, AI-generated issues stay separate from organic development, and sensitive automation logic remains in a private repository. Use it for workflow experimentation, centralized automation across multiple repositories, or managing workflows for repositories you don't directly control. ## How It Differs from MultiRepoOps @@ -44,8 +35,6 @@ While [MultiRepoOps](/gh-aw/patterns/multi-repo-ops/) runs workflows **from** yo └─────────────────┘ └──────────────────┘ ``` -In SideRepoOps, workflows run in GitHub Actions **on the side repository** but perform operations (create issues, PRs, comments) **on the main repository** using cross-repository authentication. - > [!TIP] > Testing with TrialOps > Before deploying SideRepoOps workflows to production, use [TrialOps](/gh-aw/patterns/trial-ops/) to test them in isolated trial repositories. This lets you validate behavior and iterate on prompts without creating real issues in your repositories. @@ -392,17 +381,8 @@ safe-outputs: This creates a feedback loop where the side repository tracks automation effectiveness. -## Related Patterns - -- **[MultiRepoOps](/gh-aw/patterns/multi-repo-ops/)** - Coordinate work across multiple repositories from main repo -- **[Orchestration](/gh-aw/patterns/orchestration/)** - Orchestrate multi-issue initiatives -- **[IssueOps](/gh-aw/patterns/issue-ops/)** - Issue-driven automation patterns +## Related -## Related Documentation +**Patterns**: [MultiRepoOps](/gh-aw/patterns/multi-repo-ops/) · [Orchestration](/gh-aw/patterns/orchestration/) · [IssueOps](/gh-aw/patterns/issue-ops/) -- [Cross-Repository Operations](/gh-aw/reference/cross-repository/) - Checkout and target-repo configuration -- [Safe Outputs Reference](/gh-aw/reference/safe-outputs/) - Complete safe output configuration -- [GitHub Tools](/gh-aw/reference/github-tools/) - GitHub API toolsets -- [Authentication](/gh-aw/reference/auth/) - Token types and precedence -- [Security Best Practices](/gh-aw/introduction/architecture/) - Authentication and security -- [Reusing Workflows](/gh-aw/guides/packaging-imports/) - Sharing workflows +**Reference**: [Cross-Repository Operations](/gh-aw/reference/cross-repository/) · [Safe Outputs](/gh-aw/reference/safe-outputs/) · [GitHub Tools](/gh-aw/reference/github-tools/) · [Authentication](/gh-aw/reference/auth/) · [Reusing Workflows](/gh-aw/guides/packaging-imports/) From 7c73a918a2f791f0c749f3609ccbe35de36657bc Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Sat, 7 Mar 2026 00:10:25 +0000 Subject: [PATCH 2/2] ci: trigger checks