chore: adds golang linting rules and fixes issues in the code

.commitlintrc.yml

@@ -0,0 +1,3 @@
+---
+extends:
+  - "@commitlint/config-conventional"

.devcontainer/devcontainer.json

@@ -12,4 +12,4 @@
       }
   },
   "remoteUser": "vscode"
-}
+}

.github/ISSUE_TEMPLATE/dev_story_template.yml

@@ -8,8 +8,8 @@
   - type: markdown
     attributes:
       value: |
-         Describe the use-case to be implemented from the user-persona point of view. 
-         There can be multiple workflows which achieve the use-case
+        Describe the use-case to be implemented from the user-persona point of view.
+        There can be multiple workflows which achieve the use-case
   - type: textarea
     id: description
     attributes:
@@ -61,11 +61,11 @@
       label: "Definition of Done"
       description: "Describe the Definition of Done, which might be a use-case demonstrated to the TWG"
       placeholder: |
-         * The required technical documentation should be updated
-         * In case of any prototyping activity, the evaluation, design and outcomes need to be documented
-         * API updates need to be updated in swagger (or other) files
-         * Test automation should be done to demonstrate the use-case
-         * Code and documentation should be pulled into the release branch and the pull-request approved by the TWG
+        * The required technical documentation should be updated
+        * In case of any prototyping activity, the evaluation, design and outcomes need to be documented
+        * API updates need to be updated in swagger (or other) files
+        * Test automation should be done to demonstrate the use-case
+        * Code and documentation should be pulled into the release branch and the pull-request approved by the TWG
     validations:
       required: true
   - type: input

.github/ISSUE_TEMPLATE/dev_task_template.yml

@@ -8,8 +8,8 @@
   - type: markdown
     attributes:
       value: |
-         Describe the Task. This may be to do a design, prototype, test or documentation.  
-         Ideally a task should be something that can be handled by an individual within a 5-6 story-points in size.
+        Describe the Task. This may be to do a design, prototype, test or documentation.
+        Ideally a task should be something that can be handled by an individual within a 5-6 story-points in size.
   - type: textarea
     id: description
     attributes:
@@ -30,7 +30,7 @@
     id: type
     attributes:
       label: Type of Story
       description: "Is this an Story for feature implementation / prototyping / learning ?"
       options:
         - Implementation
         - Prototyping
@@ -42,7 +42,7 @@
     id: related
     attributes:
       label: "Related Tasks"
       description: "Which other tasks does this issue relate to, other than the parent Story"
       placeholder: "GitHub issue #1234 or None"
     validations:
       required: true
@@ -51,10 +51,10 @@
       value: |
         Describe the "Definition of Done", which can be presented or reviewed
         * The required technical documentation should be updated
         * In case of any prototyping activity, the evaluation, design and outcomes need to be documented
         * API updates need to be updated in swagger (or other) files
         * Test automation should be done to demonstrate the use-case
         * Code and documentation should be pulled into the release branch and the pull-request approved by the TWG
   - type: dropdown
     id: status
     attributes:

.github/ISSUE_TEMPLATE/feedback.yml

@@ -1,7 +1,7 @@
 name: "Feedback"
 description: "An open feedback form for the Margo Code First Sandbox"
 title: "[FB: ]"
-labels: ["DRAFT","Feedback"]
+labels: ["DRAFT", "Feedback"]
 assignees:
   - "nilanjan-samajdar"
 body:
@@ -18,13 +18,13 @@
   - type: markdown
     attributes:
       value: |
-         Please provide full details regarding your feedback towards the Code First sandbox below.
-         If referring to specific files in documentation or code, please provide file-name and line-number.
+        Please provide full details regarding your feedback towards the Code First sandbox below.
+        If referring to specific files in documentation or code, please provide file-name and line-number.
   - type: textarea
     id: feedback
     attributes:
       label: "Feedback"
       description: "Feedback"
       placeholder: "I sense a disturbance in the logic—care to bring balance with your review?"
     validations:
       required: true

.github/workflows/lint-commit.yml

@@ -0,0 +1,25 @@
+name: Lint Commit Messages
+on:
+  push:
+    branches:
+      - main
+      - develop
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  lint-commit:
+    runs-on: ubuntu-24.04
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          fetch-depth: 0 # Required to fetch all commits in the PR history
+      - name: Install commitlint
+        run: npm install -D @commitlint/cli @commitlint/config-conventional
+      - name: Validate PR commits
+        # Lints from the PR base branch to the current head
+        run: |
+          npx commitlint --from ${{ github.event.pull_request.base.sha }} \
+            --to ${{ github.event.pull_request.head.sha }} --verbose

.github/workflows/quality-gates.yml

@@ -0,0 +1,74 @@
+name: Quality Gates
+
+on:
+  push:
+    branches:
+      - main
+      - develop
+  pull_request:
+
+permissions:
+  contents: read
+  pull-requests: read
+
+jobs:
+  lint-yaml:
+    runs-on: ubuntu-24.04
+    steps:
+      - uses: actions/checkout@v6
+      - uses: ibiqlik/action-yamllint@v2
+        with:
+          file_or_dir: .github docker-compose helmchart poc
+          format: github
+          config_data: |
+            extends: relaxed
+            rules:
+              line-length:
+                max: 80
+                level: warning
+              indentation: disable
+
+
+  lint-go:
+    runs-on: ubuntu-24.04
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-go@v6
+        with:
+          go-version: 1.24.4
+      - uses: golangci/golangci-lint-action@v9
+        with:
+          version: v2.11
+
+  lint-container-manifests:
+    runs-on: ubuntu-24.04
+    steps:
+      - uses: actions/checkout@v6
+      - name: Install Helm
+        uses: azure/setup-helm@v3
+      - name: Lint Helm charts
+        run: helm lint ./helmchart
+      - name: Validate docker-compose files
+        run: |
+          docker compose -f docker-compose/docker-compose.yaml config > /dev/null
+
+  test-go:
+    runs-on: ubuntu-24.04
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-go@v6
+        with:
+          go-version: 1.24.4
+      - name: Run tests with coverage
+        run: go test -v -coverprofile=coverage.out ./...
+      - name: Check coverage threshold
+        run: |
+          COVERAGE=$(go tool cover -func=coverage.out | grep total | awk '{print $3}' | sed 's/%//')
+          echo "Code coverage is: ${COVERAGE}%"
+          # NOTE: we are printing the test coverage but not failing the pipeline as of now
+          # once the test cases are there and code coverage threshold is decided
+          # then we will enforce the minimum threshold check
+          # and can push to codecov as well
+          # if (( $(echo "$COVERAGE < 80" | bc -l) )); then
+            # exit 1
+          # fi