Quality gate
A quality gate is a checkpoint or criterion that determines whether work or an artifact meets specified requirements before proceeding to a later stage.
"Looks Good to Me"
A required validation or authorization that must be completed before a software change can advance in a delivery process.
- How it is used
- Protects code review by moving routine quality checks into merge-blocking validations.
- How deep it goes
- Defines PR gates, workflow placement, and machine-inspected criteria, but does not detail individual tool implementations.
- Examples
- Uses linting, formatting, sensitive-information checks, security checks, and GitHub’s prebuild merge check.
- What you can do after
- Apply it via pull-request checks and CI/CD gates to reserve human review for high-stakes issues.
Automating API Delivery
A security quality gate is a pipeline control that permits progression only when security evaluation results satisfy a defined threshold.
- How it is used
- Applies automated controls before API proposals reach governance review or progress through deployment.
- How deep it goes
- Defines inputs, outputs, actors, triggers, risks, and controls, but leaves project-specific control selection open.
- Examples
- Uses BookInc's inconsistent BookStore API and a 42Crunch GitHub Actions security audit with a configurable passing score.
- What you can do after
- Operate/configure pipeline checks that block proposals failing defined API quality or security thresholds.
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
- How it is used
- Coordinates infrastructure change reviews and delivery pipelines before production deployment.
- How deep it goes
- Defines review and test checkpoints, then explains staged delivery and batching risks without detailing gate implementation.
- Examples
- Uses change requests, peer review, testing environments, automated tests, and manual production approval as concrete gate artifacts.
- What you can do after
- Operate/configure delivery workflows that validate infrastructure changes before production release.
Think Like a Software Engineering Manager
A quality gate is a release-control condition that must be satisfied before software can proceed to a later delivery stage.
- How it is used
- Uses deployment-pipeline conditions to prevent unready or badly timed changes from reaching production.
- How deep it goes
- Defines gates and gives representative conditions, but does not detail their implementation or configuration.
- Examples
- Uses test coverage rules, date and time restrictions, and product launch-date constraints as deployment blockers.
- What you can do after
- Operate deployment pipelines with conditions that block production releases until readiness or timing requirements are met.
Read how Think Like a Software Engineering Manager explains quality gate →
Shipping Go: Develop, deliver, discuss, design, and go again
A quality gate is a checkpoint that evaluates a product or work output before it proceeds to a subsequent production or delivery stage.
- How it is used
- Uses automated tests as an early pipeline checkpoint before building or shipping software.
- How deep it goes
- Explains the staged rationale and demonstrates test-before-build configuration, while deferring additional guards, builds, and deployments.
- Examples
- Uses a QA conversation, a cooking analogy, and a GitHub Actions workflow running Go tests before the build.
- What you can do after
- Operate/configure a CI pipeline that tests changes before allowing dependent build work to run.
Read how Shipping Go: Develop, deliver, discuss, design, and go again explains quality gate →
Related concepts
- pipelinepart of · A pipeline is an ordered or coordinated sequence of connected processing stages or tasks that passes data, work, or results toward an outcome.
- fidelitymeasures · Fidelity is the degree to which an output, model, or representation accurately reflects or is supported by its relevant source, target, evidence, or behavior.
- software artifactuses · A software artifact is a persistent work product or object produced or maintained during software development or a related workflow.
- large language modeluses · A large language model is a machine-learning model, typically neural, trained on extensive text data to process and generate language.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.