Build flag to disable formatting generated code always

[sheki]

Running gofumpt today means “magic” modes: directories skip generated files (so they stay gofmt-style), but feeding the file list directly—like pre-commit
does—marks every file as explicit, so gofumpt rewrites the generated code. That inconsistency keeps tripping people up; This should really gate this behind a flag (e.g. --allow-generated) instead of relying on how arguments were passed.

[mvdan]

Have you seen #180 (comment) and the following discussion?

I also see that https://github.com/TekWizely/pre-commit-golang has a hook which runs gofumpt on the entire project. That would be my recommendation, as it also ensures that the entire repo is consistently formatted at all times.

[sheki]

thanks. following the discussion from #180, vendoring is no longer an issue.

For codebases that can add protofiles or mocks (with go:generate) there is no great way to filter out generated code, unless I run an grep for '// generated' , before passing it to gofumpt.

I suspect the behavior of listing all files is with pre-commit and would not change with pre-commit-golang (unless pre-commit-golang) was adopted from the start. Plus pre-commit-golang has many things we do not want to adopt right now in our large repo.