✨ DevOps - Implement PR Description Quality Check

Requested by: @wicksipedia via YakShaver.ai 🦬
cc: @wicksipedia, @calumjs, @bradystroud, @uly1, @adamcogan, @christianmorfordwaitessw

Hi Team!

🟥  Watch the video (1 min 12 sec)

  Url from screen share: https://github.com/SSWConsulting/SSW.Rules.Content/pull/10176

Pain

Implement a PR check that blocks pull requests from being merged if the description is inadequate or automatically generated without meaningful content. This will ensure that all PRs have clear and informative descriptions, detailing what changed and why.

Acceptance Criteria

1. A PR cannot be merged if the description contains only emojis or is automatically generated without meaningful content.
2. The system should identify and block PRs with descriptions that are inadequate or only contain phrases like 'automatically generated by TinaCMS'.
3. Provide feedback to the user on why the PR is blocked and what needs to be improved in the description.
4. Ensure that the feature is integrated into the existing PR workflow without disrupting other functionalities.

Screenshot

Figure: PR descriptions lack detail, need automatic blocking for inadequate descriptions.

No files or tests are named. Start by inspecting the repository's existing pull-request workflow and how TinaCMS-generated descriptions enter it. Define checks for emoji-only and automatically generated descriptions, then verify that blocked PRs receive actionable feedback without affecting other workflow behavior.