Skip to content

feat(github): require the PR template sections on core - #150

Draft
vemboy200 wants to merge 2 commits into
OpenHomeFoundation:mainfrom
vemboy200:feat/pr-template-sections
Draft

vemboy200 wants to merge 2 commits into
OpenHomeFoundation:mainfrom
vemboy200:feat/pr-template-sections

Conversation

@vemboy200

@vemboy200 vemboy200 commented Nov 11, 2026 •

Copy link
Copy Markdown

Proposed change

implements

What was said in #54
When a section of a pr template thats not meant to be deleted gets deleted in the core repo it gets flagged by the ha bot

tests

I've tested locally (so no actual comments) this against 200 prs, 192 passed, 6 were PRs from bots, which were skipped and 2 were failures.

The two that failed were
home-assistant/core#192030
home-assistant/core#191967
both have deleted a portion of the template

Type of change

  • Dependency upgrade
  • Bugfix
  • New rule or command
  • New repository manifest (enable the bot on another repo)
  • New feature (which adds functionality to an existing engine)
  • Code quality improvement or refactor (incl. tests)

Additional information

draft until i finish reviewing code
this only covers the core repo, follow ups will be made for other repos. However since the rule lives in src/github/rules it can be reused in other repos easily.

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass (mise run test). Your PR cannot be merged unless tests pass.
  • Lint and type checks pass (mise run check).
  • The code has been formatted (mise run format).
  • Tests have been added to verify that the new code works.
  • There is no commented out or debug code in this PR.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If behaviour, configuration, or environment variables changed:

  • README.md and .env.example have been updated accordingly.

vemboy200 and others added 2 commits November 11, 2026 09:22
Adds a generic pr-template rule that fails when the PR description drops
one of the configured template sections or leaves a required one empty.
Enabled on core for Proposed change, Type of change and Checklist.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A `### Details` heading inside `## Proposed change` ended the section,
so a filled-in description read as empty. Sections now run until the
next heading of the same or a higher level.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

Fail PRs that drop the template or leave Proposed change empty

1 participant