[workshop] Add node: Extend Your Agent Across Multiple Repositories

[github-actions]

Adds a new advanced-track node, Extend Your Agent Across Multiple Repositories (workshop/30-cross-repository-operations.md), extending from Step 29 (Teach Your Agent Domain Knowledge with Skills). It teaches safe-outputs.*.target-repo for writing output to a separate tracking repository and tools.github.allowed-repos (with the required min-integrity field) for restricting cross-repo reads, both backed by an additional PAT or GitHub App token.

This closes a real curriculum gap: every prior step operates within a single repository, but organizations — especially enterprise ones — frequently need one workflow to read from or write to a separate repo (e.g. a central compliance-tracking repo). Both YAML frontmatter snippets were validated with agenticworkflows compile.

Serves learners on the advanced "Go Deeper" track who have completed the skills step and want to compose workflows across repository boundaries, with an enterprise-relevant framing (PAT/App auth, GHES/GHEC note).

Warning

Firewall blocked 3 domains

The following domains were blocked by the firewall during workflow execution:

• github.github.com
• raw.githubusercontent.com
• registry.npmjs.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "github.github.com"
    - "raw.githubusercontent.com"
    - "registry.npmjs.org"

See Network Configuration for more information.

Generated by 🎓 Workshop Author · copilot · auto · 246.1 AIC · ⌖ 8.89 AIC · ⊞ 10.3K · ◷

• expires on Sep 14, 2026, 7:15 PM UTC