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
I have a problem with the Github (Enterprise instance) Sync feature, it looks like the plugin is trying to use an incorrect URL pattern which doesn't match the one which is used in the enterprise instance of Github. So the //repos and //branches parts are being added, in my case it should be: github.domain.com/design-system/tokens-v2/ but instead it tries to connect to github.domain.com/design-system//repos/tokens-v2//branches. Changing the value in the baseURL field doesn't help. Please see the details in the attached screenshot from the Add new credentials panel and the dev-tools.
Is it a bug?
Additionally, wanted to ask more about the Enterprise instance of Github, if the repo is behind a firewall and only accessible when client is connected to a VPN, will the plugin be able to access the repo?
The text was updated successfully, but these errors were encountered:
john777is
changed the title
Github Enterprise Sync issue
Github Enterprise repo URL issue
May 19, 2022
Hello,
I have a problem with the Github (Enterprise instance) Sync feature, it looks like the plugin is trying to use an incorrect URL pattern which doesn't match the one which is used in the enterprise instance of Github. So the
//repos
and//branches
parts are being added, in my case it should be:github.domain.com/design-system/tokens-v2/
but instead it tries to connect togithub.domain.com/design-system//repos/tokens-v2//branches
. Changing the value in the baseURL field doesn't help. Please see the details in the attached screenshot from the Add new credentials panel and the dev-tools.Is it a bug?
Additionally, wanted to ask more about the Enterprise instance of Github, if the repo is behind a firewall and only accessible when client is connected to a VPN, will the plugin be able to access the repo?
The text was updated successfully, but these errors were encountered: