You are here:
Work Outside the DevOps Center UI
Use your preferred local development tools to work on next-generation DevOps Center work items and commit changes directly to source control. After merging your changes, complete the promotion in DevOps Center.
Required Editions
| Available in: Lightning Experience in Professional (API access required), Enterprise, Performance, Unlimited, and Developer Editions |
| Not Available in: Government Cloud Plus. Contact your Salesforce account executive for more details. |
| Not available in: EU Operating Zone. EU Operating zone is a special paid offering that provides an enhanced level of data residency commitment. DevOps Center is supported in orgs in the EU that aren’t part of EU OZ, per standard product terms and conditions. |
Note This feature works differently in the next-generation DevOps Center and DevOps Center
(Managed Package). This information pertains to the next-generation DevOps Center. To learn
about this feature in DevOps Center (Managed Package), see Work Outside DevOps Center
(Managed Package).
| User Permissions Needed | |
|---|---|
| To work outside and commit change to the DevOps Center source control: | DevOps Center User in DevOps Center Hub org |
Create a work item in DevOps Center. See Create and Assign Work Items.
- In DevOps Center, select an existing work item.
-
Change the work item status to In Progress.
DevOps Center creates a feature branch in your repository and displays the branch URL.
Tip Alternatively, you can create a branch manually from the first pipeline stage's branch. Name the branch using your work item number. For example, WI-000015. - Open your local terminal or IDE, and check out the feature branch.
- Develop and test changes locally.
- Commit your changes, and push the feature branch to your remote repository.
- In your source control repository, create a pull request (PR) from your feature branch to the first pipeline stage branch (Integration).
-
Review, approve, and merge the pull request.
Your changes may take a few moments to appear in DevOps Center. For metadata and data changes, wait for DevOps Center to sync your remote changes before acting on related objects. For non-metadata changes, such as updates to the .forceignore file, you can continue with the promotion immediately.
- In DevOps Center, open the work item, and change its status to Ready to Promote.
Your Deployment Manager can now go to the DevOps Center Pipelines tab and complete the promotion. See External Merges.
Did this article solve your issue?
Let us know so we can improve!
