🔧 Integrate golangci-lint for Static Code Analysis

[Saurabh2402]

• To improve code quality and maintain consistency across the project, I'd like to propose adding golangci-lint to the development workflow.
• Relying solely on code reviews for style and bug detection, which is less efficient and more error-prone than automated linting.
• This tool helps catch common bugs, enforces style guidelines, and ensures adherence to Go best practices—all with minimal setup and configuration.

Why this matters:

1. Identifies potential bugs early through static analysis
2. Maintains consistent code style and formatting
3. Reduces technical debt over time
4. Speeds up code reviews with automated checks

Proposed steps

1. Add a formatter section in the [.golangci.yml] linter file and format the entire codebase.
2. This will rearrange imports and remove unnecessary whitespaces.
3. Introduce only the staticcheck linter and lint the codebase to catch common bugs and issues.
4. Add govet and gocritic linters, then lint the codebase again to catch more subtle issues.
5. Ensure linting runs automatically on pull requests by integrating it into the CI/CD pipeline.
6. Gradually add more useful linters as needed and lint the codebase accordingly.

I would like to take ownership of implementing this proposal. Please let me know if there are any specific requirements or preferences before I begin.

[duke-git]

@Saurabh2402
Hi Saurabh:

Thank you for proposing the integration of golangci-lint to enhance code quality and consistency—it’s a very good initiative. I fully agree with adding it to our development workflow, as automated linting will streamline reviews and reduce errors.

To ensure alignment, let’s prioritize ensuring that all contributors apply golangci-lint in their local development environments. This will prevent code style inconsistencies before changes reach the CI/CD pipeline.

Your proposed steps (configuring .golangci.yml, phased linter integration, and CI/CD integration) sound well-planned. Feel free to proceed with ownership of the implementation—no additional requirements from my end, please loop in the team if you need input on linter rules or setup details.

Looking forward to seeing this roll out!