Hey, bitrise.yml-in-repo people 
You store your bitrise.yml in Git so that you have version history, code review, the whole team working from a single source of truth.
There were two problems.
First, the Workflow Editor only loaded your config from the default branch. Working on a feature branch? You’d have to mentally translate what you were seeing to what was actually there. Not ideal.
Second, every time you made a change, you had to leave. Copy or download the new YAML. Open your repo. Find the file. Paste. Commit. Push. A round trip nobody designed, nobody wanted, and nobody had time for. A tax on doing the right thing.
The result? Most of you just went back to your IDE or the local CLI. And quietly gave up on the Workflow Editor altogether. Which meant missing out on everything it offers that local editing can’t: conflict warnings, language server, stack and plan validation, trigger map validation, secrets, licenses, and machine management. All of it. Left on the table.
Both problems are fixed.
Start from the right branch
You’re no longer locked to your default branch. Load your config from any branch before you start editing. Working on a feature branch? Load from there. Reviewing a colleague’s config? Load from there. The editor goes where the work is.
Make a change. Push it. Done.
The Workflow Editor now pushes directly to your repository. Make your change, write a commit message, choose your branch, and that’s it. No clipboard. No context switching. No “wait, did I paste the right version?”
Three ways to save
- Push to your current branch - commits directly and keeps you in flow.
- Create a new branch - when you want to push to a different branch than the current one.
- Manual update - download or copy the YAML and commit it yourself. The old way, still there if you need it.
The best thing to happen to your bitrise.yml since Git itself. Your repo. Your branches. Your editor. All working together, at last. Happy building