Summary
Currently developers use the inbuilt environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.
We are now adding a new extensible mechanism to enable customers and partners to create their own custom protection rules to gate their deployments and make them more secure.
Intended Outcome
Customers and partners can extend Environment protection rules to integrate with other services and control the promotion of deployments across environments.
How will it work?
With the new custom deployment protection rules, you can create your own protection rules to use in your workflows or share the rules you build with the GitHub community. Developers can find a suitable “protection rule”and enable it in their production and high valued environments.
Summary
Currently developers use the inbuilt environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.
We are now adding a new extensible mechanism to enable customers and partners to create their own custom protection rules to gate their deployments and make them more secure.
Intended Outcome
Customers and partners can extend Environment protection rules to integrate with other services and control the promotion of deployments across environments.
How will it work?
With the new custom deployment protection rules, you can create your own protection rules to use in your workflows or share the rules you build with the GitHub community. Developers can find a suitable “protection rule”and enable it in their production and high valued environments.