Improve quality checks with GitHub Actions and standardized configuration

[Copilot]

Modernizes quality checks by replacing npm-based tooling with GitHub Actions and standardizing linter configurations.

Changes

• Workflow updates (build_on_push.yaml):

  • Replace markdownlint-cli with DavidAnson/markdownlint-cli2-action@v22
  • Replace cspell with streetsidesoftware/cspell-action@v8
  • Add ibiqlik/action-yamllint@v3 for YAML validation
  • Remove Node.js setup step

• Configuration standardization:

  • Simplify .markdownlint.json to DemaConsulting standard (MD003: atx, MD007: indent 2, MD013: 120 chars)
  • Add .yamllint.yaml with exact specification from issue (allows on: keyword, 120 char limit, proper indentation rules)

• YAML formatting fixes:

  • Format spdx-workflow.yaml to comply with yamllint rules (add document start, fix indentation)
  • Remove trailing spaces in .github/dependabot.yml
  • Remove trailing spaces in .github/workflows/weekly-maintenance.yml
  • Remove trailing spaces in .github/ISSUE_TEMPLATE/bug_report.yml

• Markdown fixes:

  • Add blank lines around lists in .github/agents/README.md (MD032)
  • Wrap long line in .github/ISSUE_TEMPLATE/bug_report.yml (line-length)

• Dictionary update:

  • Add yamllint to .cspell.json dictionary

Validation

All quality checks pass:

markdownlint-cli2 "**/*.md"     # 0 errors
cspell "**/*.{md,cs}"           # 0 issues  
yamllint -c .yamllint.yaml .    # 0 errors (warnings only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Feature]: Improve Quality Checks</issue_title>
<issue_description>### Problem Statement

The project should improve quality checks

Proposed Solution

The proposed solution includes:

1. Modify the build_on_push.yaml 'quality-checks' job to run markdownlint using DavidAnson/markdownlint-cli2-action@v22
2. Modify the build_on_push.yaml 'quality-checks' job to run cspell using streetsidesoftware/cspell-action@v8
3. Add yamllint checking to the build_on_push.yaml 'quality-checks' job using ibiqlik/action-yamllint@v3
4. Update the .markdownlint.json file to comply with DemaConsulting standard formatting
5. Fix any issues found by the changes

Alternatives Considered

No response

Usage Examples

Benefits

Improved file consistency

Priority

Medium - Would improve my workflow

Willingness to Contribute

Yes, I can submit a pull request

Additional Context

The .markdownlint.json should be modified to:

{
  "default": true,
  "MD003": { "style": "atx" },
  "MD007": { "indent": 2 },
  "MD013": { "line_length": 120 },
  "MD033": false,
  "MD041": false
}

The .yamllint.yaml file should be:

---
# yamllint configuration for TestResults
# This configuration defines the rules for YAML file linting

extends: default

rules:
  # Allow 'on:' in GitHub Actions workflows (not a boolean value)
  truthy:
    allowed-values: ['true', 'false', 'on', 'off']
    check-keys: true

  # Allow longer lines for URLs and complex expressions
  line-length:
    max: 120
    level: error

  # Ensure proper indentation
  indentation:
    spaces: 2
    indent-sequences: true

  # Ensure proper comment formatting
  comments:
    min-spaces-from-content: 2

Checklist

• I have searched existing issues to ensure this is not a duplicate
• I have provided a clear description of the feature
• I have explained why this feature would be useful</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Feature]: Improve Quality Checks #40

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.