ci: enforce and document Conventional Commits for PR titles

[wmmc88]

Summary

Updates CONTRIBUTING.md with comprehensive Conventional Commits guidance and adds a GitHub Action to enforce it on PR titles.

Builds on the earlier work in #298 by @leon-xd.

Changes

CONTRIBUTING.md

• Expanded the PR title requirements into a dedicated section
• Documented all valid commit types with descriptions (feat, fix, docs, ci, chore, etc.)
• Defined crate names as the valid optional scopes (cargo-wdk, wdk, wdk-alloc, wdk-build, wdk-macros, wdk-panic, wdk-sys)
• Clarified that scope is optional and should be omitted for cross-cutting changes
• Documented breaking change syntax with examples
• Added real examples drawn from the repo history

.github/workflows/lint-pr-title.yaml

• Added \�mannn/action-semantic-pull-request@v6\ to validate PR titles
• Configured allowed scopes to crate names only (optional)
• Uses \pull_request_target\ trigger (safe for fork-based PRs)
• Includes sticky PR comment via \marocchino/sticky-pull-request-comment@v2\ for contributor-friendly error messages that auto-delete when resolved

Context

This repo already follows Conventional Commits in practice but it was not explicitly documented or enforced. This PR formalizes the existing convention. The action uses the default commitizen types which cover all types currently used in the repo (chore, fix, ci, refactor, feat, docs, test, style, build, perf, revert).

34 other Microsoft repos already use this same action, including SynapseML, terraform-provider-fabric, fabric-sdk-go, and oxidizer.

Supersedes #298.

[Copilot]

Pull request overview

This PR updates the CONTRIBUTING.md file to mandate the Conventional Commits specification for PR titles and bodies (since PRs are squash-merged), and fixes a stale branch reference. It supersedes #298.

Changes:

• Added guidance to use the Conventional Commits specification for both PR title and body
• Fixed stale master branch reference to main in the rebase instruction
• Cleaned up and clarified the "Submitting a Pull Request" bullet points (reformatted for readability)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.42%. Comparing base (e1821cd) to head (2bc8a5f).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #623   +/-   ##
=======================================
  Coverage   77.42%   77.42%           
=======================================
  Files          24       24           
  Lines        4851     4851           
  Branches     4851     4851           
=======================================
  Hits         3756     3756           
  Misses        978      978           
  Partials      117      117           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

.github/workflows/lint-pr-title.yaml:63

• This == null condition likely never matches because missing step outputs are exposed as empty strings in GitHub Actions expressions. As a result, the sticky error comment may never be deleted after the title is fixed. Consider checking for an empty string (and/or gating with success()).

      - name: Delete error comment when resolved
        if: ${{ steps.lint_pr_title.outputs.error_message == null }}
        uses: marocchino/sticky-pull-request-comment@v2

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.