Some environments, such as
production, should be protected so that only qualified people can affect them. This is particular important for manual actions such as
deploy to production, but could apply to automatic actions as well. This is similar, but slightly different than protected branches. Depending on how protected branches evolves, protecting environments may not be necessary. Or vice versa.
- Use an interface similar to protected branches
Environments can be used for different scopes, so some of them is just for testing while another is for production. As deploy jobs could be raised by different users with different roles, it is very important that specific environments are "protected" to avoid unauthorized people to affect them. This feature ensures that only people with the right privileges can deploy code to the "protected" environments, keeping them safe.