One team wants long-lived develop and release branches before production deploy. Another wants merge-to-main as the production trigger. Both must map onto CodePipeline. Which branching structures are those?
Select an answer to reveal the explanation.
Short Explanation
One team wants long-lived develop and release branches. Another wants merge-to-main as the production trigger. Gitflow is the long-lived path; GitHub Flow is merge-to-main. Swapping the names is the trap.
Full Explanation
Gitflow uses long-lived develop and release branches before production. GitHub Flow uses merge-to-main as the production trigger. Both can invoke CodePipeline. Swapping the names is the trap. Translate is not a flow, and CodePipeline can start from a branch event.