The pipeline fired. The code was ready. But it wasn’t shipping—not yet.
That was the rule.
A human had to say yes. A real, deliberate yes. Not just to a pull request. Not just to a green check mark. To the final push that could move code into production. That moment—the gap between automation and release—is where query-level approval lives.
In GitHub Actions, Continuous Integration and Continuous Deployment (CI/CD) can be fully automated. But full speed without control is a liability. Query-level approval is the gate that lives inside the workflow. It forces a pause, a checkpoint, a conscious decision before the pipeline hits its final step.
This isn’t the same as a review in GitHub. Reviews happen earlier—usually before merging to the main branch. Query-level approval happens when the change has passed tests, built successfully, maybe even been deployed to staging. It’s the last defense. The place where deployment risk turns into deployment confidence.
The beauty of query-level approval in GitHub CI/CD is that it can be embedded directly in the workflow YAML. This gives you three key advantages:
- Enforced Human Verification – Stop bad code or incomplete changes from ever reaching production.
- Contextual Awareness – Review logs, artifacts, metrics, or security scans before approving.
- Granular Control – Approve deployments selectively based on target environment, time windows, or compliance needs.
It’s simple to set up. Inside your GitHub Actions workflow, you add a manual_approval job that waits for a user to approve before continuing. You can structure it so only specific teams or users hold release power. This satisfies security requirements, meets compliance mandates, and keeps surprises out of production.
Query-level approval also aligns with controlled deployment strategies. It pairs naturally with canary releases, feature flags, and staged rollouts. It stops you from treating production deploys like merges—because they’re not the same thing.
If you run sensitive workloads, you need this. If your product uptime is tied to revenue, you need this. If a single bad deployment could take hours to roll back, you definitely need this.
The future of CI/CD is speed with safety. You can get both. And you can see it in action.
Set up CI/CD query-level approval today with hoop.dev—and watch it run live in minutes.