|Content Last Reviewed||
This direction is constantly evolving and everyone can contribute:
GitLab supports teams collaborating and building software together, however that collaboration is only available inside GitLab application.
Developers, on the other hand, spend the majority of their time working in local editors implementing work outlined in issues, responding to merge request feedback and testing/debugging their applications. These tasks are the core of the developer experience, but GitLab is missing from this experience in any integrated way.
GitLab should support developers closer to where they're doing their meaningful work and enable them to be more efficient in the delivery of that work.
There are many specific problems that can be solved by focusing on local developer tooling:
In progress: VS Code Extension Housekeeping &3350
GitLab has recently adopted a VS Code Extension. In order to make the project ready for contributing and future development some general housekeeping needs to be done.
Next: Remote Development Environments &3230
Developing a strategy and MVC for enabling developers to test and debug their applications utilizing remote compute will be key in expanding in this path.
We're not currently focused on extensions for any other local editors or IDEs. We recognize there are a variety of these environments and we'll continue to monitor demand and market trends to look for other opportunities to support developers.
The editor group is also not looking to connect our existing Web IDE to any runtime environments or local tools for further development. We may continue to explore a more advanced Web IDE that could support these itmes in the future.