Installed git hub is commit a4b5580678f18a9f91c0783250f2850383be58ec.
When I redirect stdout for a specific repository git hub forks exits with status 1.
For a different repository the status is 0.
When not redirecting stdout the problematic repository is not a problem anymore.
Removing the --git-dir option I used and the behaviour is all the same.
(The CWD is outside any git checkout)
As such I am suspecting that git hub forks has an issue with the repository itself, and not the local checkout for it. Trying the command on a different machine and I see the same issue.
Something in the intersection of the specific repository (mattijk/consio) and stdout a terminal vs redirected to a file for git hub forks is trouble.
Here is my session for one the boxes, still all with --git-dir.
Installed git hub is commit
a4b5580678f18a9f91c0783250f2850383be58ec
.When I redirect stdout for a specific repository
git hub forks
exits with status 1. For a different repository the status is 0. When not redirecting stdout the problematic repository is not a problem anymore.Removing the
--git-dir
option I used and the behaviour is all the same. (The CWD is outside any git checkout)As such I am suspecting that
git hub forks
has an issue with the repository itself, and not the local checkout for it. Trying the command on a different machine and I see the same issue.Something in the intersection of the specific repository (
mattijk/consio
) and stdout a terminal vs redirected to a file forgit hub forks
is trouble.Here is my session for one the boxes, still all with
--git-dir
.