GitHub Dev Workflow Implementation

[viraj89]

Description

This issue focuses on setting up and implementing a structured GitHub development workflow for the dev team. The workflow includes lifecycle management of changes, code reviews, policy enforcement, branching strategy, and automated checks to streamline the development process.

A detailed document prepared by Ashish is available here: GitHub Dev Workflow Document

Goals

• Implement a structured GitHub workflow.
• Define and enforce a branching strategy.
• Automate code review and reviewer assignment.
• Set up GitHub Actions for testing, linting, and coverage checks.
• Enforce protected branch rules for beckn-onix-v1.0 and dev branches.
• Add CODEOWNERS file for automated reviewer assignment.
• Add .golangci.yml file for linting configuration.
• Create a GitHub Action for CI/CD pipeline.
• Validate the workflow with a dummy commit.

Expected Outcome

A well-defined GitHub development workflow that ensures code quality, structured review processes, and automated checks to maintain high coding standards.

Acceptance Criteria

• beckn-onix-v1.0 and dev branches are marked as protected with enforced rules.
• Feature, release, and hotfix branching strategies are followed.
• CODEOWNERS file is added to the repository.
• .golangci.yml file is added for linting checks.
• GitHub Actions workflow is implemented and passes tests.
• Code coverage threshold is set to 90%.
• Dummy commit validates the setup and workflow execution.

Mockups / Wireframes

NA

Product Name

Beckn ONIX

Domain

NA

Tech Skills Needed

• Git & GitHub
• Go Programming Language
• CI/CD with GitHub Actions
• Linting and Code Quality Tools
• Code Review Best Practices

Complexity

High

Category

Development Process

Sub Category

Version Control & CI/CD