Closed
Description
your feature request related to a problem? Please describe.
When working in a multiple services environnent it can be hard to maintain and to update lint rules at the team/project level.
When a library is no more maintained or with a big security issue, adding the rule to stop using it for each project can be pretty time consuming.
Describe the solution you'd like.
Maintaining a single repository with lint rules for the project/team.
With a CI/CD pipeline pushing the latest rules to an S3 bucket , nexus repository or something else.
Then for each project/service the Makefile would be like:
.PHONY: lint
lint:
golangci-lint run --config=https://team.repository.com/lint/.golangci-lint.yaml
Describe alternatives you've considered.
- Using git submodules: It become as time consuming as updating the configuration file for each services,
- Cloning the repository for each CI pipeline to retrieve the lastest configuration file: Developpers needs to do it on their dev computer too, bad dev experience.
Additional context
Here is the implementation pull request: #2136