Reusable workflows

Centralized workflow_call components only pay off if teams actually call the current version. This page manages that adoption.

What you getCopy Anchor Link

• Catalog — every reusable workflow in the organization in one inventory.
• Caller dependency graph — each repository and workflow that calls a given component, so blast radius is visible before a breaking change.
• Version distribution — how many callers are on @v1.0.0 vs @v2.0.0, tracking migration progress.
• Diff viewer — workflow definitions compared between releases.
• Schema documentation — auto-extracted inputs, outputs, and secrets with a copyable caller uses: block, so consumers call it correctly the first time.

PR impact alertsCopy Anchor Link

Turn on Pull Request Comments in Settings → System and every PR that opens or updates while touching a reusable workflow gets an automatic Reusable Workflow Alert comment — the changed workflows (and whether inputs/secrets changed), the list of repositories and files that call them, and a review checklist. The comment updates in place on each push, so reviewers always see the current blast radius of the change.

Typical workflowCopy Anchor Link

1. Release @v3 of a shared workflow.
2. Check the version distribution to see remaining @v1/@v2 callers.
3. Open the caller graph to find their repositories and file upgrade PRs.