We’ve added new capabilities to the Language Server
We’ve added an autocomplete function so now you can hover for documentation, catch errors in real time, navigate between definitions and references, and press ctrl+space to autocomplete workflow names, step identifiers, inputs, and more — all without leaving the editor.
Available on all Bitrise plans, including Hobby.
The Problem
Most Bitrise customers manage their CI configuration by storing bitrise.yml in their repo and editing it by hand. The syntax is dense, pipelines reference workflows that reference other workflows, and there’s no feedback until you push and something breaks.
Getting a step input wrong, misspelling a workflow name, or adding a utility workflow to a pipeline by accident — the first signal any of these happened is a failed build, usually a few minutes in, after the VM has already spun up and the queue has moved on.
There’s no reason editing YAML should feel like working blind. Your code editor knows your code. Your Bitrise editor should know your config.
What is available to help with writing bitrise.yml?
The Language Server ships four capabilities for the Workflow Editor YAML view.
Autocomplete
Press ctrl+space anywhere in your YAML to see valid suggestions for that position. The list filters as you type.
Autocomplete covers:
- Workflow IDs, pipeline IDs, and stage IDs
- Step bundle IDs and container IDs
- Step names and step versions
- Step input fields
You’re never guessing at a string that has to be exactly right.
Contextual documentation
Hover over any step name or step input to see its description inline — what the step does, what a parameter expects, what values are valid. No more alt-tabbing to the docs mid-edit.
- Hover a step name → step description
- Hover a step input → input description and accepted values
- Hover a workflow name in a pipeline definition → workflow description
Syntax validation
The Language Server flags errors as you type — no build required to find out something’s wrong. Mistakes are underlined inline, the same way a code editor highlights a type error.
Validation catches:
- Workflow names that don’t exist in your config
- Actions that aren’t permitted, like referencing a utility workflow inside a pipeline
- Typos, incomplete definitions, and incorrect use of parameters
Rich code navigation
Navigate complex configs without scrolling. Available via cmd+click, F12, or right-click.
-
Go-to-definition — jump from a reference to where something is declared. Editing a pipeline that references
build,test, anddeploy? Jump directly to any of those workflow definitions.
-
Go-to-reference — start from a definition and see everywhere it’s used. Before renaming or removing a workflow, see every pipeline or stage that includes it. Covers workflows, step bundles, and containers.
How to Start
Everything is available now in the Workflow Editor → Configuration YAML view. No setup, no feature flag, no bitrise.yml changes required.
The YAML editor uses Monaco under the hood — the same engine as VS Code — so the keyboard shortcuts are identical:
ctrl+space— trigger autocompletecmd+clickorF12— go to definition or reference- Right-click — full navigation menu
What’s Next
VS Code support is planned for a future release — all of the above will be available when editing bitrise.yml locally in your IDE.
Happy building! 