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
Using Github Enterprise Server 3.9.6 with Microsoft.SourceLink.GitHub 8.0.0.
SourceLink is using the /raw path on the main GitHub URL when it should be using the raw. subdomain.
Example of the URL generated:
https://github.INTERNAL_URL/raw/ORG_URL/REPO_URL/1e045336c6c208f216b8e2b2cbb3036a6f4ab41f/CPlusPlusProject/CPlusPlusProject.cpp
Should be:
https://raw.github.INTERNAL_URL/ORG_URL/REPO_URL/1e045336c6c208f216b8e2b2cbb3036a6f4ab41f/CPlusPlusProject/CPlusPlusProject.cpp
GitHub Enterprise Servers can be configured either way, but GitHub recommends using sub-domains for isolation. I'm not sure if there's a way to detect which is actually in use. I would imagine a DNS lookup to see if the raw. domain exists would be sufficient.
The text was updated successfully, but these errors were encountered:
We have several thousand repositories on our GitHub Enterprise Server instance, configuring it across all of them will be a bit difficult to coordinate. I'm uncertain if there is any way to know the raw url config without making network requests, which would generally break determinism.
Using Github Enterprise Server 3.9.6 with Microsoft.SourceLink.GitHub 8.0.0.
SourceLink is using the
/raw
path on the main GitHub URL when it should be using theraw.
subdomain.Example of the URL generated:
https://github.INTERNAL_URL/raw/ORG_URL/REPO_URL/1e045336c6c208f216b8e2b2cbb3036a6f4ab41f/CPlusPlusProject/CPlusPlusProject.cpp
Should be:
https://raw.github.INTERNAL_URL/ORG_URL/REPO_URL/1e045336c6c208f216b8e2b2cbb3036a6f4ab41f/CPlusPlusProject/CPlusPlusProject.cpp
GitHub Enterprise Servers can be configured either way, but GitHub recommends using sub-domains for isolation. I'm not sure if there's a way to detect which is actually in use. I would imagine a DNS lookup to see if the
raw.
domain exists would be sufficient.The text was updated successfully, but these errors were encountered: