What is a destination branch in the context of Copado?

In the context of Copado, a destination branch refers to the version of the code that is targeted for deployment, specifically within a source control system. It is essentially a copy of the content included in the destination environment, which is where the changes being promoted will ultimately reside after a successful deployment process. This branch holds the latest updates and changes that have been merged, allowing teams to keep track of what is intended to go live or be tested in a specific environment.

To clarify the other options: while a backup of all user stories may be an important aspect of project management, it does not directly relate to the concept of a destination branch. Temporary storage of metadata changes is more aligned with staging operations before finalizing changes, rather than defining a permanent destination for those changes. Lastly, a list of all environments used during deployment provides important context for deployment management but does not define what a destination branch is; rather, it refers to multiple deployment locations rather than a singular branch or copy of code. Therefore, the understanding of a destination branch within Copado focuses specifically on the targeted code repository for deployment.