---
schema_version: "1"
id: 47417ecd3e8c3e95e3c0910656dc9f2c12a13e678e312738fbcd64321b4c3e43
title: devops promote
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/sfclireference/guides/devops/cli_reference_devops_promote.md
canonical_url: https://developer.salesforce.com/docs/platform/salesforce-cli-reference/guide/cli_reference_devops_promote.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 0168599a71cdf80cf6c5917ab0a961905f288e024d1a6c80addb6d2641ac87ee
products:
- Salesforce CLI Command Reference
- salesforcedx
---
# devops promote
Promote work items or a pipeline stage to a target pipeline stage.
## Description for devops promote
Promote specific work items or all approved work items from a source stage to the target pipeline stage.
Pass --work-item-id to promote one or more specific work items to the target stage.
Pass --stage-id to promote all approved work items from that source stage to the target stage.
Exactly one of --work-item-id or --stage-id must be provided.
Use --deploy-all to deploy all metadata in the branch rather than only changes not yet in the target stage.
## Flags
| Flag Name (Long) | Flag Name (Short) | Description |
|------------------|-------------------|-------------|
| ‑‑api‑version | N/A | **Type:** Value
Override the api version used for api requests made by this command |
| ‑‑deploy‑all | ‑a | **Type:** Boolean
Deploy all metadata in the branch to the stage's org.
If you don’t specify this flag, only changes in the stage’s branch are deployed. |
| ‑‑flags‑dir | N/A | **Type:** Value
Import flag values from a directory. |
| ‑‑json | N/A | **Type:** Boolean
Format output as json. |
| ‑‑skip‑validation | N/A | **Type:** Boolean
Skip pre-promote validation. By default, promotion is validated before proceeding to prevent promoting work items without an associated PR. Use this flag to bypass validation. |
| ‑‑stage‑id | ‑s | **Type:** Value
ID of the source pipeline stage whose approved work items will be promoted. Mutually exclusive with --work-item-id. |
| ‑‑target‑org | ‑o | **Type:** Value
**Required**
Username or alias of the target org. Not required if the `target-org` configuration variable is already set. |
| ‑‑target‑stage‑id | ‑t | **Type:** Value
**Required**
ID of the pipeline stage to promote to. |
| ‑‑test‑level | ‑l | **Type:** Value
**Valid Values:** `NoTestRun`, `RunSpecifiedTests`, `RunLocalTests`, `RunAllTestsInOrg`
Deployment Apex testing level.
Valid values are:
- NoTestRun — No tests are run. This test level applies only to deployments to development environments, such as sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.
- RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and trigger individually and is different than the overall coverage percentage.
- RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked packages. This test level is the default for production deployments that include Apex classes or triggers.
- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.
If you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more information, see the section "Running Tests in a Deployment" in the "Metadata API Developer Guide". (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm) |
| ‑‑tests | N/A | **Type:** Value
Apex tests to run when --test-level is RunSpecifiedTests.
Separate multiple test names with commas. Enclose the entire flag value in double quotes if a test name contains spaces. |
| ‑‑work‑item‑id | ‑i | **Type:** Value
ID of the work item to promote. Mutually exclusive with --stage-id.
Specify this flag multiple times to promote multiple work items in a single operation. |
## Examples for devops promote
Promote all approved work items from a source stage to a target stage:
```shell
sf devops promote --target-org my-devops-org --stage-id 1QVxx0000000001 --target-stage-id 1QVxx0000000002
```
Promote a specific work item to a stage:
```shell
sf devops promote --target-org my-devops-org --work-item-id 1fkxx0000000001 --target-stage-id 1QVxx0000000001
```
Promote multiple work items:
```shell
sf devops promote --target-org my-devops-org --work-item-id 1fkxx0000000001 --work-item-id 1fkxx0000000002 --target-stage-id 1QVxx0000000001
```
Promote a stage with full deploy:
```shell
sf devops promote --target-org my-devops-org --stage-id 1QVxx0000000001 --target-stage-id 1QVxx0000000002 --deploy-all
```