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
When the codebase was changed to use direct Git file reading, instead of libgitsharp, a regression was introduced.
The regression is that when resolving refs, the new code fails to take into account existence of the packed-refs file. Therefore, if HEAD points to a packed ref, sourcelink will not be able to find the commit hash, and will fail with the message "Repository has no commit."
This especially impacts TeamCity, since it appears to be writing the packed-refs file directly, instead using the normal git fetch workflow, which means that unlike most build scenarios, HEAD will be pointing to a packed ref, rather than a loose one.
The text was updated successfully, but these errors were encountered:
When the codebase was changed to use direct Git file reading, instead of libgitsharp, a regression was introduced.
The regression is that when resolving refs, the new code fails to take into account existence of the
packed-refs
file. Therefore, if HEAD points to a packed ref, sourcelink will not be able to find the commit hash, and will fail with the message "Repository has no commit."This especially impacts TeamCity, since it appears to be writing the packed-refs file directly, instead using the normal
git fetch
workflow, which means that unlike most build scenarios, HEAD will be pointing to a packed ref, rather than a loose one.The text was updated successfully, but these errors were encountered: