-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Gitlab #356
Comments
I totally agree with this! It's so powerful extension we definitely need support for GitLab! |
@delold @svipben I'm happy you're excited about this! To build this extension, we introduced a new proposed api for adding comments that is meant to be generic (in the release notes here: https://code.visualstudio.com/updates/v1_27#_comment-providers). This extension is meant only to add support for GitHub pull requests - trying to make it integrate with other git providers would make it bloated. Instead, we plan to create a separate extension for each git provider. |
Omg, thank you very much!🔥 |
@RMacfarlane don't know about your planning Progress - Just wanted to point to GitLab Workflow, created by Fatih Acet over at GitLab. Perhaps its worth talking with him. |
I have created a VSCode extension for GitLab called GitLab Workflow. It supports creating MRs, issues and pipelines directly from VSCode. You can also see pipeline status, MR link and closing issue link on the VSCode status bar. Feel free to take a look at it https://marketplace.visualstudio.com/items?itemName=fatihacet.gitlab-workflow |
@fatihacet GitLab Workflow is truly awesome for gitlab users! It would be great if we can add review comments within VSCode |
Hi @fatihacet 👋 Awesome extension! The comment provider API is still being stabilized and there are a lot of things I would like to add to it. Would welcome your feedback here: microsoft/vscode#53598 |
Can't we have a |
Have any other git providers implemented anything using comments yet? Anything in the works? |
It would be amazing if this extension would support Gitlab too.
The text was updated successfully, but these errors were encountered: