Hi! We're (@adafruit) a user of this action, and we get the following notification when it runs:

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: jenschelkopf/issue-label-notification-action

If this won't be possible, please let us know so that we can look for an alternative.

Thank you.

I've got a config ala:

jobs:
  notify:
    runs-on: ubuntu-latest
    steps:
        - uses: jenschelkopf/[email protected]
          with:
             recipients: |
                  help wanted=@org-name/team-name

When the help wanted label is applied I see the comment posted as expected, but the team mention (@org-name/team-name) does not cause notifications to be sent.

Notably this does work for individual mentions (@krukow) but not for org-namespaced/team names @org/team

I've validated that if I create a comment using curl + REST, I do get the results as expected, so I believe the difference must be in this action or in octokit/rest.js?

i.e. this correctly notifies the team:

curl \
  -X POST \
  -H "Accept: application/vnd.github.v3+json" -H "Authorization: token [REDACTED]" \
  https://api.github.com/repos/[redacted]/[redacted]/issues/[N]/comments \
  -d '{"body":"Heads up @org-name/team-name - the 'help-wanted' label was applied to this issue."}'

I am working on a scenario that a GitHub action workflow will fire when issues are created.

Not working - bot labels the issue
If the issue contains specific text then an action will automatically add a label to the issue using the context of a bot. In this scenario the issue label notification never fires.

Example
BrianTJackett/issue-notification-workflow#11

Working - user labels the issue
If I change the auto labeler to use a personal access token (PAT) the label is added as my own account and not a bot. In this scenario the issue label notification does fire.

Example
BrianTJackett/issue-notification-workflow#12

Is there a reason why this action would not fire when a bot labels the issue? Thanks for providing this community action and any help you can offer.

Looks like this action broke with an API change maybe?

obspy/obspy#3074

Does this workflow also notify emails on github discussions too?

When the action posts a comment, the email notification that one gets doesn't have any context other than the title of the issue. This means I get notified, but I always have to click in to open the issue in the browser to understand what issue the label was added to.

I think if the action instead modified the issue description, appending a line like

cc @someuser @anotheruser

it would instead include the whole issue body text in the email notification, the same way that it is included when e.g. being assigned to an issue.

What do you think about having an option for this?

Here's my workflow. When I create / add a 'bug' label to an issue, the notification isn't sent. Any help would be awesome!!