Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[build] use WorkingDirectory for <GitBlame/> #2594
Downstream in monodroid, I'm getting a build failure such as:
If I run the git command manually:
It seems we shouldn't be using a full path here, but use
This has somehow been working in the past, so perhaps my version of
Don't know what happened to the build...
I got the same error when I rebased: #2590
The problem isn't the full path (and we want the full path, just for sanity).
The problem is that your git checkout is (partially) FUBAR.
Unfortunately I can't readily find how to fix a FUBAR repo, short of nuking it and checking it out again.
For example, a few weeks ago I moved my git checkout from one directory into another.
That's the new dir, not the old dir, but the problem is that it's a full path, so when I moved my git checkout, the path was invalidated, and every
I had to find and manually edit each of these in order to get
Regardless, using a full path should be perfectly valid, and if
What we can do is improve the error message. What we currently generate is not helpful, because the actual
We should fix that: surface the
So I did a fresh checkout and I'm still having the problem with our private repo:
But this command works fine:
That's why I'm wondering if we can set
$ cd $HOME $ git blame /path/to/Configuration.props
When within a git repo, using a full path Works For Me™
$ cd /path/to/xamarin-android $ git blame /path/to/xamarin-android/Configuration.props # no error
Which suggests that we should accept this PR, to decrease git version dependencies.