You can log any of your favorite GitLab servers and start your great job!
The GitLab Extension for Visual Studio provides GitLab integration in Visual Studio 2015/2017. Most of the extension UI lives in the Team Explorer pane, which is available from the View menu.
The Visual Studio Extension is also available at the Visual Studio Marketplace, or by searching for GitLab4VS in the Visual Studio extension manager. The latest build of the Visual Studio Extension is available at the Open VsixGallery
For the new version of Gitlab:
- https//gitlab.com or your GitLab server
- input your email address or username
- your password (not the token)
- use "GitLab ApiV4 Oauth2" don't use "API v4" as the instructions direct
- Two-Factor : Off
For older versions of Gitlab
- Your GitLab server
- input your email address or username
- your password (not the token) 1.use "GitLab ApiV3 Oauth2" or "API v3"
by Brett Winters
- In GitLab, [top right] go to Settings then Access Tokens (left menu)
- Enter a name & expire time (optional).
- Check off "api" as the scope.
- Click "Create Personal Access Token". This will appear in a textbox at the TOP of the page.
- In Visual Studio, click "Connect" beside GitLab.
- Enter your GitLab Username and paste in the Access Token.
- Change it to "API v4" instead of "API v4 OAUTH2".
- Make sure "Two Factor Authentication" is CHECKED.
- Save. You're DONE.
If you create a personal access token (https://yourgitlaburl.com/profile/personal_access_tokens) and select 2fa and use your ldap username + your PAT you will be able to login and use the plug-in.
by dominicdejacomo
V1.0.189
Thanks Rennerdo30
V1.0.183
- Fix for " cannot connect to custom gitlab server with different port #50
V1.0.160
- Automatically detects the API version of Gitlab
V1.0.156
- Visual Studio 2019 support
V1.0.150
- AddOpen URL from clipboard
- Support Gitee.com
- fix #35
V1.0.0.122
Fix HttpUtility.UrlEncode processing username or email causing problems that cannot be logged in
V1.0.0.119
Now update login mode is OAuth2, which can't be logon before because the new version of GitLab's API session has been discarded.
The two API login methods are supported in the login interface, and the old version of GitLab needs to be selected manually. The default is that the login mode is OAuth2 and V4 !
V1.0.0.115
1.You can select GitLab Api version .
V1.0.0.112
1.modify "Open On GitLab" to "GitLab"
V1.0.0.95
- French, Japanese, German and other languages have been added, but these are Google's translations, so we need human translation!
- Open on GitLab move to submenu!
- Fixed issue #3,Thanks luky92!
- The selected code can create code snippets directly
- When you create a project, you can select namespases.
- GitLab's Api is updated from V3 to V4.
V1.0.0.70
- GitLab login information associated with the solution, easy to switch GitLab server.
- Enter the password and press enter to login GitLab server.
- Now, We can login with two factor authentication.just enter the personal access token into the password field.
V1.0.0.58
- Support for Visual Studio 2017
- Fix bus.
V1.0.0.40
- Right click on editor, if repository is hosted on GitLab Server , you can jump to master/current branch/current revision's blob page and blame/commits page. If selecting line(single, range) in editor, jump with line number fragment.
- Fix #4 #5 #6 Official builds of this extension are available at the official website.
HomePage http://visualstudio.gitclub.cn/
https://github.com/maikebing/GitLab.VisualStudio/issues
https://marketplace.visualstudio.com/items?itemName=MysticBoy.GitLabExtensionforVisualStudio
https://gitee.com/GitGroup/CodeCloud.VisualStudio
https://github.com/neuecc/Open-on-GitHub
https://github.com/Xarlot/NGitLab https://github.com/Franklin89/NGitLab https://github.com/maikebing/NGitLab