Hi team,
When using the Next-Gen DevOps Center, I don’t see an option to commit changes. I wanted to confirm if I’m missing a step in the new process.
For example, let’s say I have the following pipeline:
Dev1 → UAT → Production
- I create a custom object, an Apex class, and a test class in the Dev1 environment.
- I create a Work Item and set the environment to Dev1.
- However, when I try to pull in the changes from Dev1, I don’t see the changes anywhere, nor do I see an option to commit them.
- In the previous DevOps Center experience, I believe this was possible through the DevOps Center package.
Could someone please clarify how we are supposed to commit/pull changes from a development environment into a Work Item using Next-Gen DevOps Center?
Is there an additional step or configuration that I’m missing?
Thanks!
That is expected — the Next-Gen DevOps Center changed WHERE the commit happens. In the old package-based DevOps Center you pulled and committed changes inside the Work Item in the app. In Next-Gen, that action moved to the DX Inspector browser extension.
The flow now:
1) Install the DX Inspector browser extension and connect it to your Dev1 environment.
2) Open your Work Item, then in DX Inspector go to the Change Management tab — that is where your changed components (custom object, Apex class, test class) show up.
3) Select them there and commit to the Work Item branch from that tab.
So you are not missing a config step in the app — the commit UI simply lives in DX Inspector now, not on the Work Item page like before. Then use development environment sync (back sync) to keep Dev1 current with the pipeline and avoid merge conflicts.
if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂
