Summary

GitHub Environments are typically used with Actions workflows to describe a general deployment target like production, testing, staging, or development to which an application or service (s) is deployed to. Currently we support “deployment protection rules” which can be configured to protect environments and their associated secrets & variables from getting accessed by unintended deployments. And also to have more controlled deployment rollouts based on certain predefined criteria evaluated by each of the rules.

However, Developers and DevOps managers often need to centrally configure and manage protection rules on their environments across their teams and applications beyond the GitHub boundaries of organizations and repositories.

To enable "Management of Environments at Scale", we are coming up with a new delightful configuration experience for defining and managing groups of Environments across repositories coupled with powerful settings management across Environments.

Intended Outcome

With this new cross-repo management experience for Environments, Developers and DevOps managers would be enabled to

• group environments within/across repos by adding metadata to environments across repositories in your organization.
• easily and consistently apply protection rules on groups of environments across repositories in order to have a standard set of configurations and settings across all environments within the group.
• filter deployment views by groups of Environments.

How will it work?

We are enabling a new central management experience for Environments across repositories by

• Extending rulesets to support central configurations on “protected Environments”
• Supporting custom properties to group Environments and configure rulesets