Roll out established MR review instructions to all Go services
## Description This work item focuses on standardizing and implementing established merge request (MR) review guidelines across all Go services within our organization to ensure consistent code quality and review practices. ## Objectives - **Standardize Review Process**: Apply proven MR review instructions to all Go service repositories - **Improve Code Quality**: Ensure consistent application of Go best practices and coding standards - **Knowledge Transfer**: Share established review patterns across all Go development teams - **Documentation**: Create or update review guidelines specific to Go services ## Scope - Identify all Go services that need the review instructions - Update repository documentation (README, CONTRIBUTING.md, or .gitlab/merge_request_templates/) - Configure any necessary CI/CD checks or automated review tools - Train team members on the standardized review process - Monitor adoption and effectiveness ## Acceptance Criteria - [ ] Inventory of all Go services completed - [ ] Review instructions documented and accessible in each repository - [ ] Team members trained on new review process - [ ] Automated checks implemented where applicable - [ ] Rollout plan executed and monitored ## Implementation Notes Consider including guidelines for: - Go-specific code review checklist - Performance considerations - Security review requirements - Testing standards - Documentation requirements This standardization will help maintain high code quality across all Go services while reducing review inconsistencies.
issue