-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Enable forbidigo linter #24278
Enable forbidigo linter #24278
Conversation
I am sure in long time Gitea still needs a lot of |
Question is whether we should allow one variant to print to stdout. In JS, a Maybe we should let |
I am neutral, it doesn't bother me 😄
IMO (ps: personally I use log.Error or break-point when debugging) |
Lint should pass now, so this is ready. There were surprisingly few issues, but I also did resort to a few per-file |
* giteaoffical/main: Improve some modal action buttons (go-gitea#24289) Enable forbidigo linter (go-gitea#24278) Fix no edit/close/delete button in org repo project view page (go-gitea#24301) Replace whitespace inside template parens during make fmt (go-gitea#24293) Upgrade act (go-gitea#24298)
Enable forbidigo linter which forbids print statements. Will check how to integrate this with the smallest impact possible, so a few
nolint
comments will likely be required. Plan is to just go through the issues and either://nolint
directive if it makes senseI don't plan on investigating the individual issues any further.
Initial Lint Results