GitHub Actions "deployment was rejected" by environment reviewers

By Kaveh Alemi·Latchkey

An environment with required reviewers gates jobs that target it. A reviewer can reject the pending deployment, which fails the job by policy - the workflow is working as configured.

What this error means

A job targeting a protected environment is held for review and then fails with "deployment was rejected", after a required reviewer declined the deployment.

Error: Deployment was rejected.

Common causes

Required reviewer declined

A reviewer assigned to the environment's protection rules rejected the pending deployment.

Deployment did not meet gate criteria

The change failed the reviewer's acceptance criteria for that environment.

How to fix it

Address the rejection and re-deploy

1. Read the reviewer's rejection reason on the environment deployment.
2. Fix the underlying issue and push a new run for re-review.
3. Confirm you are requesting the correct environment and reviewers.

Audit environment protection rules

1. Open Settings > Environments > <env> and review required reviewers.
2. Confirm the reviewer list and wait timer are intended.
3. Adjust the rules only with proper authorization.

How to prevent it

• Communicate deployment intent so reviewers can approve promptly.
• Keep environment protection rules and reviewer lists accurate.
• Surface rejection reasons to the team for fast follow-up.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions