Dynamic required messages

[desrosj]

In 900dc32, both the pr_message and issue_message were marked as required parameters in run(), but neither was noted as required: true in the action.yml file.

When a repository only wants to welcome new contributors on pull requests (or vice versa), then a non-empty message needs to be specified for the other event type.

This removes that requirement by dynamically marking the respective message input based on the triggering event. This is a bit of a different approach to #404, which removes all required: true designations in favor of enforcing the requirement through conditional blocks.

Fixes#365.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR updates the GitHub Action logic so only the relevant input message is required (issue vs PR), and expands the test suite to validate the new required-input behavior.

Changes:

• Refactor run() to read a single message input based on whether the event is an issue or a pull request.
• Update compiled dist/index.js to match the source change.
• Add tests covering “non-required” and “required missing” scenarios for issue_message / pr_message.

Reviewed changes

Copilot reviewed 2 out of 5 changed files in this pull request and generated 4 comments.

File	Description
src/main.ts	Reads only the applicable input (issue_message or pr_message) and uses it as the comment body.
dist/index.js	Compiled output updated to reflect the new input selection logic.
badges/coverage.svg	Coverage badge SVG regenerated/updated.
tests/main.test.ts	Reworks getInput mocking and adds targeted tests for required input behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 5 changed files in this pull request and generated 1 comment.