Which action triggers the creation of a Feature Branch in Copado?

The creation of a Feature Branch in Copado occurs when changes are committed to the user story. This action is significant because it represents the moment when development work transitions from planning into actual implementation. By committing changes, developers are effectively tying their work directly to the user story they are addressing, allowing for clearer tracking and management of that particular feature's progress.

The Feature Branch serves as a dedicated space where the specific changes can be made without affecting the main branch or other ongoing work. It enables parallel development efforts, thereby enhancing collaboration and minimizing the risk of conflicts. Once changes are committed, the branch is created to encapsulate those changes, facilitating further refinement and eventual integration back into the main codebase.

Other actions, such as approving a user story or initiating a deployment, do not directly trigger the creation of a Feature Branch. Approving a user story relates more to the validation of the proposed work rather than the execution. Initiating a deployment pertains to moving code to a different environment, while adding a new component is an action that may be part of a workflow but does not independently trigger the creation of a Feature Branch. Thus, committing changes is the pivotal action that leads to the establishment of the Feature Branch.