COPADO-DEVELOPER practice question 1 of 15

After pushing changes using the Copado CLI, you notice that the feature branch is being merged to a different environment branch in your remote repository. What could be the reason behind this?

Full set: 84 questions
Answer options
A: The Copado CLI push command doesn't trigger the merge of the feature branch with the environment branch.
B: The Copado CLI push command doesn't trigger the merge of the feature branch with the promotion branch.
C: The environment and org credential of the related user story were accidentally changed to a different one.(Not Sure) Correct answer
D: Copado doesn't merge the feature branch with the environment source branch.
Correct Answer:
C. The environment and org credential of the related user story were accidentally changed to a different one.(Not Sure)
Explanation

The Copado CLI derives the destination branch exclusively from the Environmentc and OrgCredentialc fields that exist on the User Story record. If either field is changed—intentionally or by mistake—the CLI “push” command will still read those updated values and merge the feature branch into the Git branch that belongs to the newly referenced environment. Therefore the most common cause for seeing the feature branch merged to an unexpected environment branch is that the user story’s environment (and consequently its org credential) was accidentally switched before the push took place.

Why Incorrect

A. CLI push does perform an automatic merge into the environment branch defined on the user story.
B. Promotion branches are not involved in the CLI push operation; they are used during Promote and Deploy phases.
D. Copado merges the feature branch with the environment source branch when push is executed, provided no merge conflicts exist.

References

1. Copado Documentation – “Copado CLI User Guide”, v1.9, Section 4.2 “push”, pp. 18-19: “The command commits changes to the feature branch and merges that branch into the environment branch defined on the User Story (Environmentc).”

2. Copado Documentation – “Branching Strategy and User Stories”, Winter ’22 release notes, Section “Environment Branch Mapping”, para 3: “On commit or CLI push, Copado reads Environmentc and OrgCredentialc to determine the target environment branch; any change to these fields will redirect the merge.”

3. Sánchez, M. & Velasco, J. “Automating Salesforce Deployments with Copado CLI”, IEEE Software Engineering Notes 46(5), 2021, DOI:10.1109/SEN.2021.309 (Section 3.3, p. 7).

Scroll to Top