11-21-2025 08:27 AM
Scenario: Two developer working on same playbook on Dev environment. For ex
Playbook Name: XXX_playbook
Developer A & Developer B working on XXX_playbook and both make changes independently. 'A' makes first commit on develop branch. Then, 'B' makes second commit. B assumes his changes are ready to be promoted to prod. But, 'A' not.
Now, if the content pack is promoted to prod, then 'A' changes also goes to prod along with 'B' which SHOULDN'T be.
Any solution to handle this scenario?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
