Summary
To encourage best practices and consistency, this feature enables you to provide centrally managed workflows across multiple repositories in your organization.

This feature includes:

• Ability to define workflow templates for an entire enterprise
• Ability to extend workflow templates, and keep the consuming workflow up to date as the template changes (aka versioning)
• Ability to create partials within a workflow template, so a consuming workflow can customize sections
• Ability to make a workflow template required

Intended Outcome
This feature is designed to give you the ability to define how flexible or strict workflow consistency should be for your organization. For example, you can require that repositories use only the workflows that are managed at the organization level. Or you can enable each repository to supplement with their own workflows.

How will it work?

Centrally managed workflows will be configured via config-as-code: files checked into GitHub.

We’re also introducing workflow partials. Workflow partials let you define required steps in a workflow while giving flexibility on some steps. For example, you can define a workflow partial that requires specific security scans but allows developers to define custom build and test steps.

Together, organization-level workflows and workflow partials enable you to achieve much more consistency across your repositories.

Related roadmap items:

• Org-level secrets
• Org-level starter workflows
• Organization and enterprise workflows
• Workflow templates in private repositories
• Use actions from private repositories