## Problem to Solve GitLab's strength is a single application for the DevOps lifecycle. However, local editors are outside of this integration and don't benefit from the features of GitLab like Code Review, CI Pipeline Feedback or general project management tasks (Issues/Epics). Engineers must write their code, push those changes to GitLab and then navigate to GitLab in their browser to start benefiting. ## Vision We want engineers to be efficient, productive and able to easily interact with GitLab in the editor they choose to work in. ## Additional Details Users of GitLab may prefer their existing local editor to the experience of editing things in GitLab's Web IDE. The benefits of GitLab's Web IDE are it's integrated experience with the other parts of GitLab (CI, Merge Requests, etc.). As we continue to expand those features, replicating them to popular local editors may also become an important part of the strategy. ## Proposal GitLab should release officially supported extensions for the most popular editors. These extensions should provider users with the feedback on their work without needing to visit the GitLab application in the browser. ### What does this look like? GitLab has a [VS Code Extension](https://gitlab.com/gitlab-org/gitlab-vscode-extension) in market with adoption already. Continuing to iterate and improve this experience is the first step in this strategy. Future plans for this extension can be tracked in the [issue tracker](https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/issues). ### What's next? Continuing to monitor market demand for additional editors to support. See also https://gitlab.com/gitlab-org/editor-extensions/meta/-/issues/49+ (internal).