A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://docs.gitlab.com/editor_extensions/visual_studio_code/ below:

GitLab Workflow extension for VS Code

The GitLab Workflow extension for Visual Studio Code integrates GitLab Duo and other GitLab features directly into your IDE. It adds a GitLab Workflow panel to the VS Code sidebar where you can view issues, merge requests, and pipelines, and extend your view with custom queries.

To get started, install and configure the extension.

When configured, this extension brings the GitLab features you use every day directly into your VS Code environment:

The GitLab Workflow extension also streamlines your VS Code workflow with AI-assisted features:

When you view a GitLab project in VS Code, the extension shows you information about your current branch:

Switch GitLab accounts in VS Code

The GitLab Workflow extension uses one account for each VS Code Workspace (window). The extension automatically selects the account when:

What the extension shows in the status bar depends on your account setup:

To select a GitLab account for the active VS Code window, select the status bar item, or:

  1. Open the Command Palette:
  2. Run the command GitLab: Select Account for this Workspace.
  3. Select your desired account from the list.
Select your GitLab project

When your Git repository can be associated with multiple GitLab projects, the extension cannot determine which account to use. This can happen when you have multiple remotes, for example:

In these cases, the extension adds a (multiple projects) label to show you must choose an account.

To select an account:

  1. On the vertical menu bar, select GitLab Workflow ( tanuki ) to display the extension sidebar.
  2. Expand Issues and Merge Requests.
  3. Select the line containing (multiple projects, click to select).
  4. Select your desired project:

The Issues and Merge requests list updates with your selected project’s information.

Change your selection

To change your project selection:

  1. On the vertical menu bar, select GitLab Workflow ( tanuki ) to display the extension sidebar.
  2. Expand Issues and Merge Requests to show the project list.
  3. Select the project.
  4. Next to the project name, select Clear Selected Project button ( close-xs ).
Use slash commands

Issues and merge requests support GitLab slash commands to perform actions directly in VS Code.

Create a snippet

Create a snippet to store and share bits of code and text with other users. Snippets can be a selection or an entire file.

To create a snippet in VS Code:

  1. Choose the content for your snippet:
  2. Open the Command Palette:
  3. In the Command Palette, run the command GitLab: Create Snippet.
  4. Select the snippet’s privacy level:
  5. Select the snippet’s scope:

GitLab opens the new snippet’s page in a new browser tab.

Create a patch file

When you review a merge request, create a snippet patch when you want to suggest multi-file changes.

  1. On your local machine, check out the branch you want to propose changes to.
  2. In VS Code, edit all files you want to change. Do not commit your changes.
  3. Open the Command Palette:
  4. In the Command Palette, enter GitLab: Create snippet patch, and select it. This command runs a git diff command and creates a GitLab snippet in your project.
  5. Enter a Patch name and press Enter. GitLab uses this name as the snippet title, and converts it into a filename appended with .patch.
  6. Select the snippet’s privacy level:

VS Code opens the snippet patch in a new browser tab. The snippet patch’s description contains instructions on how to apply the patch.

Insert a snippet

To insert an existing single-file or multi-file snippet from a project you are a member of:

  1. Place your cursor where you want to insert the snippet.
  2. Open the Command Palette:
  3. Type GitLab: Insert Snippet and select it.
  4. Select the project containing your snippet.
  5. Select the snippet to apply.
  6. For a multi-file snippet, select the file to apply.
View issues and merge requests

To view issues and merge requests for a specific project:

  1. On the menu bar, select GitLab Workflow ( tanuki ) to display the extension sidebar.
  2. On the sidebar, expand Issues and merge requests.
  3. Select your desired project to expand it.
  4. Choose one of the following result types:

Select an issue or merge request to open it in a new VS Code tab.

Review a merge request

Use this extension to review, comment on, and approve merge requests without leaving VS Code:

  1. While viewing issues and merge requests in VS Code, select the merge request you want to review. Its sidebar entry expands with more information.

  2. Under the merge request’s number and title, select Description to read more about the merge request.

  3. To review the proposed changes to a file, select the file from the list to show it in a VS Code tab. GitLab shows diff comments inline in the tab. In the list, deleted files are marked in red:

Use the diff to:

Compare with default branch

To compare your branch with your project’s default branch, without creating a merge request:

  1. Open the Command Palette:
  2. In the Command Palette, search for GitLab: Compare current branch with master and press Enter.

The extension opens a new browser tab. It shows a diff between the most recent commit on your branch, and the most recent commit on your project’s default branch.

Open current file in GitLab UI

To open a file from your current GitLab project in the GitLab UI, with specific lines highlighted:

  1. Open your desired file in VS Code.
  2. Select the lines you want to highlight.
  3. Open the Command Palette:
  4. In the Command Palette, search for GitLab: Open active file on GitLab and press Enter.
View security findings

Prerequisites:

To view security findings:

  1. On the vertical menu bar, select GitLab Workflow ( tanuki ) to display the extension sidebar.
  2. On the sidebar, expand Security scanning.
  3. Select either New findings or Fixed findings.
  4. Select a desired severity level.
  5. Select a finding to open it in a VS Code tab.
Perform SAST scanning

History

Static application security testing (SAST) in VS Code detects vulnerabilities in the active file. With early detection, you can remediate vulnerabilities before you merge your changes into the default branch.

When you trigger a SAST scan, the content of the active file is passed to GitLab and checked against SAST vulnerability rules. GitLab shows scan results in the primary side bar.

To learn about setting up SAST scanning, see SAST scanning in VS Code on GitLab Unfiltered.

Prerequisites:

To perform SAST scanning of a file in VS Code:

  1. Open the file.

  2. Trigger the SAST scan by either:

  3. View the results of the SAST scan.

    1. View the Primary Side Bar.
    2. Select GitLab Workflow ({tanuki}) to display the extension sidebar.
    3. Expand the GITLAB REMOTE SCAN (SAST) section.

    The results of the SAST scan are listed in descending order by severity. To see details of a finding, select it in the GITLAB REMOTE SCAN (SAST) section of the extension sidebar.

Search issues and merge requests

To search your project’s issues and merge requests directly from VS Code, use filtered search or Advanced Search. With filtered search, you use predefined tokens to refine your search results. Advanced Search provides faster, more efficient search across the entire GitLab instance.

Prerequisites:

To search the titles and description fields in your project:

  1. In VS Code, open the Command Palette:
  2. Select your desired search type: GitLab: Search project merge requests or GitLab: Search project issues.
  3. Enter your text, using filter tokens as needed.
  4. To confirm your search text, press Enter. To cancel, press Escape.

GitLab opens the results in a browser tab.

Filter searches with tokens

Searches in large projects return better results when you add filters. The extension supports these tokens for filtering merge requests and issues:

Token Example Description assignee assignee: timzallmann Username of the assignee, without @. author author: fatihacet Username of the author, without @. label label: frontend or label:frontend label: Discussion A single label. Usable more than once, and can be used in the same query as labels. labels labels: frontend, Discussion, performance Multiple labels in a comma-separated list. Can be used in the same query as label. milestone milestone: 18.1 Milestone title without %. scope scope: created-by-me or scope: assigned-to-me or scope: all. Issues and merge requests matching the given scope. Values: created-by-me (default), assigned-to-me or all. title title: discussions refactor Issues and merge requests with title or description matching these words. Don’t add quotation marks around phrases.

Token syntax and guidelines:

You can combine multiple tokens in a single search query. For example:

title: new merge request widget author: fatihacet assignee: jschatz1 labels: frontend, performance milestone: 17.5

This search query looks for:

Customize keyboard shortcuts

You can assign different keyboard shortcuts for Accept Inline Suggestion, Accept Next Word Of Inline Suggestion, or Accept Next Line Of Inline Suggestion:

  1. In VS Code, run the Preferences: Open Keyboard Shortcuts command.
  2. Find the shortcut you want to edit, and select Change keybinding ( pencil ).
  3. Assign your preferred shortcuts to Accept Inline Suggestion, Accept Next Word Of Inline Suggestion, or Accept Next Line Of Inline Suggestion.
  4. Press Enter to save your changes.
Update the extension

To update your extension to the latest version:

  1. In Visual Studio Code, go to Settings > Extensions.
  2. Search for GitLab Workflow published by GitLab (gitlab.com).
  3. From Extension: GitLab Workflow, select Update to {later version}.
  4. Optional. To enable automatic updates in the future, select Auto-Update

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4