Automate GitHub PR Reviews with Branch Policy, Scoring, and Slack Alerts

Introduction

Speed up code reviews and enforce standards automatically. This workflow scores each PR, approves or requests changes, stores results, and alerts the right people ✅

Trigger Event

• Triggered when a GitHub pull request is opened or updated in the selected repository.

Actions

• First, the branch name is checked against your policy (e.g., feature_via_YYYY-MM-DD_autonumber). If the PR was opened from an invalid branch, the workflow immediately requests changes on GitHub and posts a Slack message to nudge the author.
• It then fetches PR file changes and finds the related task entry from your work tracking table using the branch name. The task details are attached to each file change for richer context.
• A scoring step reviews the combined context (ratings, reasons, prior rejections) and returns a clear decision: Approve or Reject, plus a numeric rating and summarized reasons.
• If approved, the workflow posts an “APPROVE” review on the PR.
• If rejected, it posts a “REQUEST_CHANGES” review on the PR with the rejection summary. It also updates the developer metrics record, incrementing the rejection count.
• The workflow stores or updates a Developers_Metrics record: pull number, PR link, AI decision, rating, assignee (from commit author), final score, and a link back to the matched task. If a record exists for that PR, it updates it; if not, it creates one.
• If a UI testing attribute appears missing in the changes, a Slack channel gets a heads‑up with the PR link so reviewers catch it early.

Benefits

• Enforce branch naming automatically; stop non‑compliant PRs early
• Faster reviews: auto‑approve simple, policy‑compliant changes
• Consistent, explainable decisions with numbered reasons
• Store review outcomes and scores for visibility and reporting
• Real‑time Slack alerts keep engineers informed without context switching
• Reduce manual errors and back‑and‑forth by standardizing checks