Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
1,322 definitions
Branch Protection is a GitOps term for repository rules that prevent unsafe merges or unreviewed source changes. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Branch Protection before lunch, so the release did not sprint into production wearing untied shoes.”
Merge Queue is a GitOps term for an ordered queue that lands approved changes after checks pass. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Merge Queue before lunch, so the release did not sprint into production wearing untied shoes.”
Required Check is a GitOps term for a status check that must pass before a source change can merge. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Required Check before lunch, so the release did not sprint into production wearing untied shoes.”
Human Approval Gate is a GitOps term for a required human decision before a change proceeds. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Human Approval Gate before lunch, so the release did not sprint into production wearing untied shoes.”
ChatOps Approval is a GitOps term for an approval or action requested through a team chat workflow. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used ChatOps Approval before lunch, so the release did not sprint into production wearing untied shoes.”
Break Glass is a GitOps term for an emergency path for bypassing normal controls with clear evidence and review. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Break Glass before lunch, so the release did not sprint into production wearing untied shoes.”
Emergency Patch is a GitOps term for a small urgent change applied to reduce active risk. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Emergency Patch before lunch, so the release did not sprint into production wearing untied shoes.”
Release Freeze is a GitOps term for a period when normal releases are paused to reduce risk. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Release Freeze before lunch, so the release did not sprint into production wearing untied shoes.”
Change Freeze is a GitOps term for a control window that limits changes during high-risk times. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Change Freeze before lunch, so the release did not sprint into production wearing untied shoes.”
Deployment Window is a GitOps term for an allowed time period for applying changes. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.
“The team used Deployment Window before lunch, so the release did not sprint into production wearing untied shoes.”