Add Environment state definitions
What does this MR do and why?
We have 3 primary user facing states for environments, but they're definitions are not concisely stated in single location.
Since these states are user facing and have specific to GitLab meaning, they should be defined in the documentation.
Clarifying these state definitions can make it simpler for users to map their own concepts of Environments to how we use them in GitLab. As precise definitions of Environments will vary, anything we can do to improve the user's experience of mapping those concepts should improve usability and communication.
Related to Clarify existing states and actions (#439405 - closed) -->
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.