You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
8. Test the refresh button for the remote branches on the WebUI, fetch from the source control menu in Studio or VS Code, and `git fetch` in Git Bash. All 3 should work without any issues.
152
152
153
+
### HTTPS Support
154
+
We recommend that people connect to their remote git repository using SSH. If you cannot use SSH connections, we also have support for HTTPS connection through OAuth2. See [our documentation for setting up an https connection](/docs/https.md).
155
+
153
156
## Support
154
157
155
158
If you find a bug or would like to request an enhancement, [report an issue](https://github.com/intersystems/git-source-control/issues/new). If you have a question, post it on the [InterSystems Developer Community](https://community.intersystems.com/) - consider using the "Git" and "Source Control" tags as appropriate.
We highly recommend that you use SSH to connect to your repositories. If this is not possible, then HTTPS is another option.
4
+
5
+
First, add your remote repo in the settings page, or during the Configure step.
6
+
7
+
After this, you have to authenticate using OAuth tokens. To do this, press "Authenticate" in the bottom left of the Embedded Git UI, or from the Source Control Menu.
8
+
9
+
### Authentication
10
+
11
+
If you have not already done so, create a new OAuth app in github or gitlab. The "Authorization callback URL" should be <your url>/isc/studio/usertemplates/gitsourcecontrol/oauth2.csp.
12
+
13
+
Remember to save the ClientID and ClientSecret. Once this is finished, you can enter your information into the authentication page.
14
+

15
+
16
+
Once all of the information is correct, you can press Save. This will redirect you to either gitlab or github in order to authorize the application to interact with this. After this is done, you will be redirected back to the authentication page, and you should be good to go!
0 commit comments