The Bitrise workflow editor now understands modular configurations.
If your Bitrise configuration is split across multiple YAML files in your Git repository, you can open, edit, and push all of them from the editor, without dropping into a local IDE.
What’s new
1. Two views to know:
- Merged config: your complete configuration, assembled and fully resolved. It is read-only.
- Module files: the individual files, which you edit in place exactly like a single
bitrise.yml.
With that, you can:
- See the whole picture in the merged view, then jump straight to the file that defines any workflow, pipeline, or step.
- Reference workflows and step bundles defined anywhere in your configuration.
Previously, editing a modular configuration in the visual editor meant flattening it into one file and losing your structure. Now that structure is preserved.
2. Push every change to Git in one commit
When you save, Bitrise gathers every changed module (here, 2 modules: bitrise/step-bundles.yml and bitrise/workflows/deploy.yml) and pushes them together. Choose the current branch or a new one, set the target branch, and write a single commit message that lands in your Git history. One action, one commit, no file-by-file work.
3. Update your repository yourself when you prefer (Screenshot 3: “Update configuration YAML”)
If you would rather apply the changes to Git by hand, choose Manual update. Bitrise lists each changed module and lets you download or copy its updated contents, so you can re-create the changes in your repository exactly. Useful when direct pushes are restricted, or when you want the commit to go through your own process.
Edit across as many files as you need, then save once. Bitrise pushes every changed module together, to a single branch, as one commit, so a set of related changes lands as one coherent update rather than a file-by-file scramble. Only the files you actually changed are written, and read-only modules included from other repositories are never touched.
Availability
Available on Enterprise plans for configurations stored in a Git repository.
Until now, editing a modular configuration in the visual editor meant flattening it back into a single file and losing your structure. Teams that organise their configuration across many files can now use the full visual editor with that structure preserved.
Read here on how to Modularize your Bitrise config
Happy YAML-ing 