[tigerblue77]

---

• I have read the contributing guideline and understand that I have made the correct modifications

---

Description:

greetings.yml.j2 now passes issue_message, pr_message and repo_token, the input names declared by linuxserver/github-workflows/.github/actions/first-interaction@v1, instead of the issue-message, pr-message and repo-token names of actions/first-interaction@v1.

Benefits of this PR and context:

closes #405

The greeting job stops failing on every opened issue and pull request of the repositories generated from this template, and first-time contributors get their message again.

How Has This Been Tested?

• Rendered the template with project_deprecation_status false and true: valid YAML whose with keys match the wrapper's inputs, and actionlint 1.7.12 reports nothing.
• Ran actions/first-interaction v3.1.0 dist/index.js locally on an opened issue event. With empty messages, which is what the wrapper passes today, it fails with Input required and not supplied: issue_message. With the messages set, it gets past the inputs to the GitHub API calls.

Source / References:

• update workflows to use linuxserver wrapper actions in templates #400, which moved the template to the wrapper
• Add workflow wrappers for checkout and first interaction actions github-workflows#66 and the wrapper's inputs: https://github.com/linuxserver/github-workflows/blob/v1/.github/actions/first-interaction/action.yml

[nemchik]

LGTM! Good Catch!

I see what happened. The upstream action switched from dashes to underscores (certainly a breaking change) and did NOT document that breaking change in a meaningful way (no mention in the release notes https://github.com/actions/first-interaction/releases/tag/v2.0.0 or readme https://github.com/actions/first-interaction/blob/main/README.md about the change, the PR actions/first-interaction#311 that did it doesn't mention it, but the code change is there).

When I wrote the composite action in our workflows repository in linuxserver/github-workflows#66 I based it on the action file in the upstream repo at the time (which had already silently switched from dashes to underscores) and did not make the appropriate changes here to our template (which you have done). Prior to switching to our composite actions in our workflows repo, we were using an old version of first-interaction which still used the dashes.