zalando / zalando/postgres-operator
Integrate in CI and align with the golangci-lint rules
Open
Nobody has claimed this yet.
enhancement
idea
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.7.1
- Where do you run it - cloud or metal? Kubernetes or OpenShift? [Bare Metal K8s]
- Are you running Postgres Operator in production? [no]
- Type of issue? [feature request]
It would be nice to have support golangci-lint in CI and golang code with the base rules.
This makes code more clear, secure and compliant.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository's CI configuration and Go source tree, then review how existing checks are defined. Integrate golangci-lint with its base rules and run the CI checks to confirm the Go code passes linting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100