-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git diff
error silenced
#18
Comments
Made a PR about this: #19. Down for a review whenever you have time ! |
Small bump on this ! |
Sorry mate, will try and get time next couple of days, but within the next
week definitely. Just on holiday not near laptop.
Bradley Falzon
…On Fri, 26 Jan 2024 at 11:23 pm, Alexandre Menasria < ***@***.***> wrote:
Small bump on this !
—
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN74UPTKHYKBGV3V7ACKSDYQOU6PAVCNFSM6AAAAAA7MZOSOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSGA3DENBSHA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
👋 Hey, no problem Bradley, I understand ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there 👋,
Stumbled upon some issues while working with golangci-lint.
Basically the fact that only the exit code is printed in the
git diff
calls in theGitPatch
function but not thegit diff
stderr makes it really hard for people to debug. I have 2 use cases from this golangci-lint issue when using thenew-from-rev
feature:new-from-rev
commit was not in the commit tree because the Github Actions runner only had a shallow clone of the repository. From the error people just understood that the diff was not working. Having the error message would have made people understand it directly.git diff
didn't work because of a diff algorithm that couldn't be found in the runner. This wasn't understandable as well because no error, only the exit code.For both issues the errors were the same:
As no one stumbled upon the seconde case I really thought I was in the same situation as the first case which made me spend a lot of time on the fix. I think it'd be a great improvment to have the error in the
fmt.Errorf
message.The text was updated successfully, but these errors were encountered: