Skip to content

Conversation

@blast-hardcheese
Copy link
Contributor

Pardon if this has been discussed before, I couldn't find it in the issue/PR list.

As a user, I find it disorienting when tools inform me that I have made a mistake but do not offer any insights into how to resolve the issue.

In this case in particular, we have all the information, but then require the user to know the defaults and to traverse the config overrides.

It'd be nice to just provide this information. Impact to existing users should be minimal, including data transfer or storage of logs in CI, since teams who are already in compliance would not get the new log component, and teams who are not in compliance yet would get the message once and then be done.

Happy to circle back if there's prior art for how this information should be displayed.

Thanks!

@boring-cyborg
Copy link

boring-cyborg bot commented May 31, 2024

Hey, thank you for opening your first Pull Request !

@CLAassistant
Copy link

CLAassistant commented May 31, 2024

CLA assistant check
All committers have signed the CLA.

@ldez ldez self-requested a review May 31, 2024 19:21
@ldez ldez added enhancement New feature or improvement linter: update Update the linter implementation inside golangci-lint labels May 31, 2024
@ldez ldez added the blocked: until next minor Will be a part of the next minor release label May 31, 2024
@ldez
Copy link
Member

ldez commented May 31, 2024

Hello, it's a good suggestion, I rephrased the message to be more explicit.

@ldez ldez removed the blocked: until next minor Will be a part of the next minor release label Jun 9, 2024
@ldez ldez added this to the next milestone Jun 9, 2024
@ldez ldez merged commit eb23eaf into golangci:master Jun 9, 2024
@ldez ldez modified the milestones: next, v1.60 Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or improvement linter: update Update the linter implementation inside golangci-lint

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants