Skip to content

feat: add atomic PR check workflow#1604

Closed
yogeshchoudhary147 wants to merge 1 commit into
mainfrom
feat/atomic-pr-check
Closed

feat: add atomic PR check workflow#1604
yogeshchoudhary147 wants to merge 1 commit into
mainfrom
feat/atomic-pr-check

Conversation

@yogeshchoudhary147
Copy link
Copy Markdown
Contributor

@yogeshchoudhary147 yogeshchoudhary147 commented May 8, 2026

Summary

Adds a GitHub Actions workflow that automatically analyses every PR targeting main for atomicity signals and posts a structured comment with the findings.

How it works

On every PR open, edit, or push, the workflow runs the following checks:

Violations (fails the check):

  • PR title contains "and"
  • Files changed >= 40
  • Total lines changed >= 1500

Warnings (advisory, check stays green):

  • Files changed >= 15
  • Total lines changed >= 400
  • Renames or moves mixed with logic changes
  • Formatting or config files mixed with source changes
  • Changes spread across more than 3 unrelated top-level areas

The bot posts a single comment on the PR and updates it on every subsequent push, no duplicate spam.

What is not changed

Branch protection rules are untouched. Nothing is enforced until the team decides to flip that switch.

Test plan

  • Raise a PR with "and" in the title, check should fail
  • Raise a clean, single-concern PR, check should pass
  • Push a new commit to an existing PR, bot comment should update not create a duplicate

@yogeshchoudhary147 yogeshchoudhary147 requested a review from a team as a code owner May 8, 2026 11:27
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 8, 2026

Atomic PR Check — Passed ✓

No atomicity concerns found. This PR looks well-scoped.

@yogeshchoudhary147 yogeshchoudhary147 changed the title feat: add atomic PR check workflow feat: add atomic PR check workflow and update config May 8, 2026
@yogeshchoudhary147 yogeshchoudhary147 changed the title feat: add atomic PR check workflow and update config feat: add atomic PR check workflow May 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant