-
Notifications
You must be signed in to change notification settings - Fork 434
update CentralRepoOps docs #17285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update CentralRepoOps docs #17285
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -15,7 +15,7 @@ Below are the key benefits of this pattern for enterprise use cases: | |||||
| - **Consistency at scale** - Same rollout logic and policy gates across all repositories | ||||||
| - **Risk reduction** - Controlled fan-out (`max`), phased prioritization, and explicit rationale | ||||||
| - **Auditability** - One orchestrator run provides a full decision trail of selection and outcomes | ||||||
| - **Operational efficiency** - Teams avoid copy-pasting workflows into every repository | ||||||
| - **Operational agility** - Update workflows in one central repository without pushing `main` changes across dozens or hundreds of repositories | ||||||
| - **Security posture** - Prioritize exposed or vulnerable repositories first | ||||||
|
|
||||||
|
|
||||||
|
|
@@ -45,12 +45,6 @@ Navigate to your central repository and create a workflow file `.github/workflow | |||||
| on: | ||||||
| schedule: | ||||||
| - cron: '0 9 * * 1' | ||||||
| workflow_dispatch: | ||||||
| inputs: | ||||||
| target_repos: | ||||||
| description: 'List of repos (owner/repo1, owner/repo2)' | ||||||
| required: false | ||||||
| type: string | ||||||
|
|
||||||
| tools: | ||||||
| github: | ||||||
|
|
@@ -60,14 +54,14 @@ tools: | |||||
| safe-outputs: | ||||||
| dispatch-workflow: | ||||||
| workflows: [dependabot-rollout] | ||||||
| max: 50 | ||||||
| max: 5 | ||||||
|
||||||
| max: 5 | |
| max: 50 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing the workflow_dispatch trigger eliminates the ability to manually trigger the workflow or specify custom target repositories. This makes the workflow only schedulable via cron, removing flexibility for ad-hoc executions. If this is intentional to simplify the documentation example, consider adding a note explaining that manual triggers can be added if needed.