Hi @GANESHPAWAR-3429 ,
Source control in ADF follows standard Git best practices when it comes to branching strategy. You should have a single central branch that each feature is branched off upon. In each feature branch, you should do all your testing and debugging so that once you merge back into the collaboration branch, you are confident the change is ready to be promoted.
For changes that you don't wish to deploy, there are a couple options.
- You can not merge back into collaboration until you are ready
- If it is a net new pipeline, don't associate with a trigger
Git operates on a commit model which allows you to easily cherry pick or revert changes if needed. Some useful links on how to best implement CICD