GitLab announces the migration of its editor by Visual Studio Code


Recently the launch of the new version of collaborative development platform GitLab 15.0 and of the most notable changes that stand out from this version, is the intention in future releases es replace web code editor built-in IDE with the Visual Studio Code editor (VS Code) developed by Microsoft with the participation of the community.

Using the VS Code editor will simplify project development in the GitLab interface and allow developers to use a full-featured and familiar code editing tool.

A survey of GitLab users showed that the web IDE is excellent to make small changes but few people use it for full coding. GitLab developers tried to understand what makes it difficult to fully work in the web IDE and came to the conclusion that the point is not the lack of specific features, but a combination of minor flaws in the interface and working methods. According to a survey by the Stack Overflow platform, more than 70% of developers use the VS Code editor, which is licensed under the MIT license, when writing code.

Way back in April 2018, GitLab 10.7 introduced the web IDE to the world and brought a lovely multi-file editor to the heart of the GitLab experience. Our goal was to make it easy for anyone to contribute, regardless of their development experience. Since its introduction, tens of millions of commits have been made from the web IDE, and we've added features like Live Preview and Interactive Web Terminals to enhance the experience. Now, we're excited to share some of the big changes we have in store for the Web IDE in upcoming milestones.

One of the GitLab engineers prepared a working prototype of VS Code's integration with the GitLab interface, which can be used to work through the browser.

GitLab Leadership considered the development promising and decided to replace the web IDE with VS Code, which would also allow you to not waste resources by adding features to the web IDE that are already in VS Code. It is planned to embed only the client-side part of the editor, integrating it with GitLab's server-side components.

In addition to significant functionality and usability improvements, the transition will provide access to a wide range of plugins for VS Code, as well as give users the ability to customize skins and control syntax highlighting. Since the introduction of VS Code will inevitably lead to editor complication, for those who need the simplest editor to make individual edits, it is planned to add the necessary editing capabilities to core components such as Web Editor, Snippets, and Pipeline Editor. .

As of the GitLab 15.0 release, the innovations added include:

  • Added visual Markdown (WYSIWYG) editing mode to Wiki.
  • The free community version integrates the functions of scanning container images for known vulnerabilities in the dependencies used.
  • Added support for adding internal notes to discussions that are available only to the author and group members (for example, to attach sensitive data to an issue that cannot be publicly disclosed).
  • Ability to link an issue to an external organization or external contacts.
  • Support for nested environment variables in CI/CD (variables can be nested within other variables, eg "MAIN_DOMAIN: ${STACK_NAME}").
  • The possibility of subscribing and unsubscribing from the user in his profile.
  • The access token revocation process has been simplified.
  • The ability to rearrange the list with problem descriptions in drag and drop mode has been provided.
  • The GitLab Workflow plugin for VS Code adds the ability to work with multiple accounts associated with different GitLab users.

Finally, if you are interested in being able to know more about this new version, you can consult the details In the following link.

The content of the article adheres to our principles of editorial ethics. To report an error click here!.

Be the first to comment

Leave a Comment

Your email address will not be published.



  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.