### Release notes Previously it was impossible for users to work on the pipeline editor in their non-main branch, in this release we are adding a branch selector to the pipeline editor, which will allow you to work on your pipeline from any branch you'd like ### Problem Currently, the pipeline editor support working from the master branch only, this limits the number of users that can use the pipeline editor since many of our users do not work directly from the master branch. ### Proposed solution We should allow pipeline editor to work from any other branch * Users should be able to select any of their existing branches * We should load the pipeline configuration based on the selected branch * Branch selector should affect all tabs in the editor (Linting, Visualization, view merged yaml) * User should be able to commit changes to the selected branch * Commit form should populate with the selected branch name * We should address the use case of switching to a branch with no file https://gitlab.com/gitlab-org/gitlab/uploads/1d0b241192fec9d5b290b44bc2551cf2/image.png ### Design From the pipeline config file list we would like to allow users to select the branch of the file they'd like to edit. | | | | ------ | ------ | |  | :link: [Figma Specs](https://www.figma.com/file/bId8kFcqoAdmAYRatTZ0ii/PA-Pipeline-Editor-2nd-iteration?node-id=362%3A10401) In case user switches branches and the file doesn't exist, as an MVC we will show an alert, then follow-up with an empty state. | | | ------ | |  | The branch selector behavior should match the behavior in the single file editor. and effect all tabs in the pipeline editor (e.g. linting, visualize)