title: CDK pipelines branching strategy
body: <p>CDK pipelines seems to only work, by default, with one branch. Am I missing something or is there a way to:</p>
  <ul>
  <li>have a dev branch to deploy to the Dev account/ env</li>
  <li>test branch deploy to Test account/env.</li>
  <li>jons-cool-feature-branch to X account/env etc</li>
  </ul>
  <p>Ideally we do not want to have to push everything to the master branch to deploy to dev / test, so that we can keep the master branch clean, tidy, and stable.</p>
  <p>I have thought about having multiple pipelines, one for dev, one for test, and one for master, this would solve the issue, but doesn’t feel like the cleanest solution.</p>
  <p>Are there any recommended patterns?</p>