Web IDE

Version history
On self-managed GitLab, by default this feature is available. To hide the feature, ask an administrator to disable the feature flag named vscode_web_ide. On GitLab.com, this feature is available.

The Web IDE is an advanced editor with commit staging. You can use the Web IDE to make changes to multiple files directly from the GitLab UI. For a more basic implementation, see Web Editor.

To pair the Web IDE with a remote development environment, see remote development.

Use the Web IDE

To open the Web IDE from the GitLab UI:

  1. On the top bar, select Main menu > Projects and find your project.
  2. Use the . keyboard shortcut.

You can also open the Web IDE from:

  • A file
  • The repository file list
  • A merge request

From a file or the repository file list

To open the Web IDE from a file or the repository file list:

  • In the upper-right corner of the page, select Open in Web IDE.

If Open in Web IDE is not visible:

  1. Next to Edit or Gitpod, select the down arrow ().
  2. From the dropdown list, select Open in Web IDE.
  3. Select Open in Web IDE.

From a merge request

To open the Web IDE from a merge request:

  1. Go to your merge request.
  2. In the upper-right corner, select Code > Open in Web IDE.

The Web IDE opens new and modified files in separate tabs and displays changes side by side with the original source. To optimize loading time, only the top 10 files (by number of lines changed) are opened automatically.

In the file tree, any new or modified file in the merge request is indicated by an icon next to the filename. To view changes to a file, right-click the filename and select Compare with merge request base.

Open a file in the Web IDE

To open any file by its name:

  1. Press Command+P.
  2. Enter the name of your file.

fuzzy_finder_v15_7

Search across files

You can use the Web IDE to search all files in the opened folder.

To search across files:

  1. Press Shift+Command+F.
  2. Enter your search term.

In the Web IDE, only partial results from opened files are displayed.

View a list of changed files

To view a list of files you changed in the Web IDE:

  • On the activity bar on the left, select Source Control, or press Control+Shift+G.

Your CHANGES, STAGED CHANGES, and MERGE CHANGES are displayed. For more information, see the VS Code documentation.

Upload a new file

To upload a new file and add it to the Git repository:

  1. In the Explorer file tree, navigate to the directory where you want to upload the file.
  2. Optional. If the directory does not exist yet, select the directory path where you want to have a new directory and either:
    • Right-click on the directory path, and select New Folder…. You can create a nested directory path with the / separator, for example parentdir/subdir1/subdir2.
    • In the Explorer panel, in the upper-right corner, select the new folder () icon.
  3. Enter the name of the new directory, and press Enter/Return to create it.
  4. Right-click on the directory path and select Upload....
  5. Select the file you want to upload, then select Open. You can select and add multiple files at once.

The file is uploaded and automatically added as a new file to the Git repository.

Switch branches

The Web IDE uses the currently selected branch by default. To switch branches in the Web IDE:

  1. On the status bar, in the lower-left corner, select the current branch name.
  2. In the search box, start typing the branch name.
  3. From the dropdown list, select the branch.

Create a branch

To create a branch from the current branch in the Web IDE:

  1. On the status bar, in the lower-left corner, select the current branch name.
  2. From the dropdown list, select Create new branch….
  3. Enter the branch name.
  4. Press Enter.

If you don’t have write access to the repository, Create new branch… is not visible.

Commit changes

To commit changes in the Web IDE:

  1. On the activity bar on the left, select Source Control, or press Control+Shift+G.
  2. Enter your commit message.
  3. Select Commit & Push.
  4. Commit to the current branch, or create a new branch.

Use the command palette

In the Web IDE, you can access many commands through the command palette. To open the command palette and run a command in the Web IDE:

  1. Press Shift+Command+P.
  2. In the search box, start typing the command name.
  3. From the dropdown list, select the command.

Edit settings

You can use the settings editor to view and modify your user and workspace settings. To open the settings editor in the Web IDE:

  • On the top menu bar, select File > Preferences > Settings, or press Command+,.

In the settings editor, you can search for the settings you want to modify.

Edit keyboard shortcuts

You can use the keyboard shortcuts editor to view and modify the default keybindings for all available commands. To open the keyboard shortcuts editor in the Web IDE:

  • On the top menu bar, select File > Preferences > Keyboard Shortcuts, or press Command+K then Command+S.

In the keyboard shortcuts editor, you can search for:

  • The keybindings you want to change
  • The commands you want to add or remove keybindings for

Keybindings are based on your keyboard layout. If you change your keyboard layout, existing keybindings are updated automatically.

Change themes

You can choose between different themes for the Web IDE. The default theme for the Web IDE is GitLab Dark.

To change the Web IDE theme:

  1. On the top menu bar, select File > Preferences > Theme > Color Theme, or press Command+K then Command+T.
  2. From the dropdown list, preview the themes with the arrow keys.
  3. Select a theme.

The active color theme is stored in the user settings.

Interactive web terminals for the Web IDE (Beta)

When you set up a remote development server in the Web IDE, you can use interactive web terminals to:

  • Access a remote shell on the server.
  • Interact with the server’s file system and execute commands remotely.

You cannot use interactive web terminals to interact with a runner. However, you can use a terminal to install dependencies and compile and debug code.

For more information about configuring a workspace that supports interactive web terminals, see remote development.