Note from maintainers: This issue describes a problem with CI config files that depend on the context set by the main .gitlab-ci.yml. The best solution reached in the comments is to allow to validate multiple …

After setting up Gitlab Workflow and using the command GitLab: Validate GitLab CI Config I get the error "Current folder doesn't contain a GitLab project". This happens even though I've setup a remote …

Summary "Validate GitLab CI config" requires project for local file import. According to GitLab's online validator and documen tation this is...

Summary Running GitLab: Validate GitLab CI config fails with 401 Unauthorized. This issue has arisen after updating to 13.8.4 from 13.7.x. Changing the Gitlab workflow to older versions does not fix. I'm …

[VS Code] Indicate included CI files are from remote when validating/merging config

However, users can not easily access the workspace level config via a command palette action like the user configuration. Proposal Add a command palette action to open the workspace level …

{ "userMessage": "Failed to parse GitLab API response", "errorMessage": "Unexpected token < in JSON at position 0", "stack": [ "SyntaxError: Unexpected token < in JSON at position 0", "\tat JSON.parse …

Sep 1, 2025 · Automatic creation of the workspace config directory and file with default settings if they don't exist Error handling for cases where no workspace is open or when file system issues occur

Nov 26, 2021 · Summary When downloading a respository via ssh protocol the repo address in .git/config contains a colon (:) after the base url. This colon causes the following error: 'Project …

Would be great to support multiple GitLab instances by overwriting the config setting in project scope. Additionally saving PAT must be reworked for making this possible.