Implement Default PR Automation (Title Checks, Auto-Labeling, and CI)

[IamLRBA]

Summary

I’d like to propose setting up GitHub Actions to standardize pull request workflows, improve code quality checks, and streamline reviews for this repo:

Proposed Automation Features

1. PR Title Validation

• Enforce a consistent commit/PR title format (e.g. “type(scope): subject”) using the Conventional Commits standard.
• Helps maintain clarity and readability of PRs.

2. Automatic PR Labeling

• Automatically label PRs based on changed files and PR content (e.g. commit type, affected components, tests, docs, etc.).
• Makes it easier for us to quickly see what a PR is about without manually labeling.

3. Monorepo-Aware CI Workflow

• Run CI jobs only for components that were changed.
• For example: run linting/tests/build only on the subproject(s) affected, not on everything.
• Speeds up CI and reduces resource usage.
• Optionally skip CI for documentation-only changes.

Proposed Benefits

• Consistent PR titles make history and changelogs cleaner.
• Automatic labeling saves maintainers and contributors time.
• CI runs become faster, focused, and efficient.
• Improves clarity for reviewers, reduces overhead, encourages good practices.

Suggested Implementation (for reference)

• Use a PR-title check action (e.g. amannn/action-semantic-pull-request) to enforce title format.
• Use a labeling action (e.g. actions/labeler) to auto-assign labels based on file paths or PR body.
• Set up a CI workflow (GitHub Actions) that detects changed subdirectories and only runs relevant jobs (lint / test / build).

How to Evaluate / Testing Plan

• Create a test PR with a valid Conventional-Commits title — title validation should pass.
• A PR touching files in a known component should automatically get the correct labels.
• Confirm that CI jobs run only for changed components.
• Confirm that documentation-only changes skip CI (if implemented).

[bahati308]

this is great, it can help us catch the bugs that slip off to deployment and break things and of course as indicated, code quality.