-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Open
Labels
enhancementNew feature or improvementNew feature or improvementlinter: customAbout custom/private lintersAbout custom/private linters
Description
Welcome
- Yes, I've searched similar issues on GitHub and didn't find any.
- I agree to follow this project's Code of Conduct
Your feature request related to a problem? Please describe
Currently golangci-lint custom write the resulting custom binary to
- The
destinationandnamespecified in .custom-gcl.yml or equivalent. ./custom-gclby default.
When building a generic harness for custom linters — one where users bring their own .custom-gci.yml files — I want to write a script that builds a custom linter and then invokes it, regardless of the destination and name specified in YAML.
Describe the solution you'd like
I want to be able to specify an output location with a command-line argument. For example, I'd like to run
$ golangci-lint custom -v -o ./freshly-built-linter
$ ./freshly-built-linter runThis can behave analagously to the -o output argument on go build: if present, override the settings in YAML.
usage: go build [-o output] [build flags] [packages]
Describe alternatives you've considered
- Requiring an implicit correspondence between arguments to my program and the contents (
name,destination) of a user's.custom-gcl.ymlfile. - Parsing the
.custom-gcl.ymlfiles in my scripts to extractnameanddestination, to recreate the path to the build target.
Additional context
No response
Supporter
- I am a sponsor through GitHub or OpenCollective
not-my-profile
Metadata
Metadata
Assignees
Labels
enhancementNew feature or improvementNew feature or improvementlinter: customAbout custom/private lintersAbout custom/private linters