rule-github-issues

To enforce GitHub issue template conventions, you can apply automated validation rules that check files matching .github/ISSUE_TEMPLATE/**/* to ensure they include required fields like name, description, labels, and body.

A pull request template should include a summary, linked issue references, testing notes, and accessibility and privacy checks to maintain consistency and guide code review processes.

Validating canonical label usage and ADR references involves checking .github/workflows/**/*.yml and documentation/**/*.md files to ensure labels and architecture decision records are consistently applied across repositories.

Yes, automating checks for conventional commit prefixes in PR titles ensures change-correctness by verifying that linked issues are properly referenced and titles adhere to project standards.

The best way to standardize GitHub workflow file configurations is to codify documented rules into automated checks that validate .github/workflows/**/*.yml files against your project's specific template conventions.

GitHub issue templates fail validation checks when they omit required structural elements such as the template name, description, labels, or body fields defined by your repository's conventions.