Create new Merge Request does not work on Gitlab.com
Checklist
-
I'm using the latest version of the extension (see the latest version in the right column of this page) - Extension version: v3.62.0
-
I'm using the latest VS Code version (find the latest version here) - VS Code version: 1.78.2
-
I'm using a supported version of GitLab (see README for the supported version) - GitLab version: "happens on
gitlab.com"
- GitLab version: "happens on
Summary
The "Create new Merge Request on current project" results in 404. There is a bug in the generated URL.
Steps to reproduce
Use the "Create new Merge Request on current project" on project hosted on gitlab.com
What is the current bug behavior?
Page is opened with 404.
https://gitlab.com/projectpath/merge_requests/new?merge_request%5Bsource_branch%5D=feature1
What is the expected correct behavior?
New MR page is opened for the project.
https://gitlab.com/projectpath/-/merge_requests/new?merge_request%5Bsource_branch%5D=feature1
Relevant logs and/or screenshots
Possible fixes
There is a missing -/ in the URL after Project path here https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/main/src/commands/openers.ts#L133. Might be related to GitLab.com update to 16.0-pre yesterday?
Edited by Peter Jakubis