Skip to main content

Environments

Environment practices help operators distinguish local development, preview behavior, and production behavior.

Operator Workflow​

  • Confirm which environment a command or browser check targets.
  • Keep local credentials out of commits and shared screenshots.
  • Use production checks only when the change is intended for production.

Verification Gates​

Verification gates: define the affected scope, run the relevant build or validation checks, perform the smallest appropriate deploy or config action, and verify the live user-facing or API behavior that changed.

For high-risk work, also prepare a rollback or follow-up plan before touching production.

Evidence To Capture​

  • Target environment and affected service, docs surface, API group, workspace, artifact, or operation.
  • Validation command or manual check performed.
  • Live route, API response, screenshot, or operation timeline proving the result.
  • Follow-up needed if verification is incomplete.

Media To Add​

  • Table: local, preview, production with purpose, typical checks, and risk level. It helps operators avoid environment mistakes. Source: release process.