Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Building with SourceLink fails when there is no Git remote named "origin"

See original GitHub issue

Noticed in https://github.com/dotnet/iot/issues/553.

I also encountered this while porting Core-Setup to Arcade, but didn’t look into it yet to find this cause. (I disabled SourceLink for now in that effort.)

Repro:

git clone https://github.com/dotnet/arcade
cd arcade
git remote rename origin dotnet
.\Build.cmd

C:\Users\dagood\.nuget\packages\microsoft.sourcelink.common\1.0.0-beta2-19351-01\build\Microsoft.SourceLink.Common.targets(50,5): error : Source control information is not available - the generated source link is empty. [D:\temp\remote\arcade\src\Microsoft.DotNet.SignTool\Microsoft.DotNet.SignTool.csproj]
...

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

tmatcommented, Jul 7, 2019

Odd, that should work. Will take a look.

1reaction

tmatcommented, Jul 7, 2019

Definitely agree that the error message could be better. https://github.com/dotnet/sourcelink/issues/324 BTW, currently we first check for origin then for any other remote (the first one). dotnet/sourcelink#306 suggests to check the remote tracking branch before falling back to origin or other remote.