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
I have one file where the push makes one line super long, and adds weird whitespace somewhere else.
I get a gofumpt error on the whitespace (first), and then on the long line (what I am referring to from here forward) I get another gofumpt error.
If I disable gofumpt, it (super weird) turns into a goimports error (but still on that long line), even though I have enabled only-new-issues: true and didn't touch the import section at all.
Then... If I turn on --fix (which the Action can't do), with gofumpt back on, I get a slew of info things (in the log) and an lll error, finally...
I mean... A few issues here:
I don't understand how or why goimports is triggering when I didn't touch the imports. Except for maybe it was using something that was imported, but since only-new-issues: true is designed to keep the issues related to what the Push or PR actually changes, it seems weird.
If the system can annotate, it would be SWELL if it could group the annotations in some way, so you aren't patching and pushing just to chase ghosts. Having all of the detected issues right there would be ideal.
The descriptions (File is not gofumpt-ed with -extra (gofumpt)) REALLY could use some translation. I feel like there is enough data there to determine what the issue is in human readable terms.
The text was updated successfully, but these errors were encountered:
ldez
transferred this issue from golangci/golangci-lint-action
Mar 27, 2021
I have one file where the
push
makes one line super long, and adds weird whitespace somewhere else.I get a
gofumpt
error on the whitespace (first), and then on the long line (what I am referring to from here forward) I get anothergofumpt
error.If I disable
gofumpt
, it (super weird) turns into agoimports
error (but still on that long line), even though I have enabledonly-new-issues: true
and didn't touch theimport
section at all.Then... If I turn on
--fix
(which the Action can't do), withgofumpt
back on, I get a slew ofinfo
things (in the log) and anlll
error, finally...I mean... A few issues here:
goimports
is triggering when I didn't touch the imports. Except for maybe it was using something that was imported, but sinceonly-new-issues: true
is designed to keep the issues related to what the Push or PR actually changes, it seems weird.File is not
gofumpt-ed with
-extra(gofumpt)
) REALLY could use some translation. I feel like there is enough data there to determine what the issue is in human readable terms.The text was updated successfully, but these errors were encountered: