Problem
Currently, the auto-comment script triggered when an issue is created is hardcoded to a static greeting text. It doesn't analyze the context of the issue title to help assign tags. Additionally, the pull request template lacks concrete validation check items (such as running npm run lint and npm run build), leading to contributors submitting PRs without running local validations.
Current Behavior
The auto-commenter responds with a boilerplate message regardless of the issue type (bug, feature request, documentation). The PR template includes a generic "I tested the change locally" checklist item instead of explicit check instructions.
Why This Improvement Is Needed
Automated labeling suggestions speed up issue classification for project maintainers. Explicit local check steps inside the PR checklist reduce the chance of broken builds in CI pipelines by reminding developers to verify their code formatting and syntax before merging.
Proposed Solution
- Update
issue-create-automate-message.yml to inspect the issue title prefixes (fix:, feat:, docs:) and inject appropriate label recommendations into the greeting message.
- Update the checklist in
PULL_REQUEST_TEMPLATE.md to require explicit validation of client linting and package compilation steps.
Expected Outcome
- New issues are greeted with dynamic classification tips.
- Contributors verify client builds before opening a pull request.
Problem
Currently, the auto-comment script triggered when an issue is created is hardcoded to a static greeting text. It doesn't analyze the context of the issue title to help assign tags. Additionally, the pull request template lacks concrete validation check items (such as running
npm run lintandnpm run build), leading to contributors submitting PRs without running local validations.Current Behavior
The auto-commenter responds with a boilerplate message regardless of the issue type (bug, feature request, documentation). The PR template includes a generic "I tested the change locally" checklist item instead of explicit check instructions.
Why This Improvement Is Needed
Automated labeling suggestions speed up issue classification for project maintainers. Explicit local check steps inside the PR checklist reduce the chance of broken builds in CI pipelines by reminding developers to verify their code formatting and syntax before merging.
Proposed Solution
issue-create-automate-message.ymlto inspect the issue title prefixes (fix:,feat:,docs:) and inject appropriate label recommendations into the greeting message.PULL_REQUEST_TEMPLATE.mdto require explicit validation of client linting and package compilation steps.Expected Outcome