tools: ping TSC members identified as inactive

[Trott]

When detecting TSC members as inactive, @-mention them in the pull
request that moves them to emeritus. This notifies them in case the pull
request is in error.

[Trott]

If we want to 100% make sure this works, we can fast-track it, close #40908, and let this open a PR.

[targos]

This lgtm, but it was mostly the next part of the message that I was interested in automating:

codebytere last attended a TSC meeting in September 2020. gabrielschulhof last attended a TSC meeting in May 2021. Neither have participated in recent votes.

[Trott]

This lgtm, but it was mostly the next part of the message that I was interested in automating:

codebytere last attended a TSC meeting in September 2020. gabrielschulhof last attended a TSC meeting in May 2021. Neither have participated in recent votes.

OK, I think this does something like that now. (I haven't tested it via an Action yet, but will run it when it lands and revise if necessary.)

[nodejs-github-bot]

Landed in f7ac6ba

[aduh95]

https://github.com/nodejs/node/runs/4315947355?check_suite_focus=true

Run gr2m/create-or-update-pull-request-action@v1
with:
    author: Node.js GitHub Bot <github-bot@iojs.org>
    branch: actions/inactive-tsc
    body: This PR was generated by tools/find-inactive-tsc.yml.
  
  @nodejs/tsc "@codebytere @gabrielschulhof"
  
  "Since 3 months ago, codebytere attended 0 out of 10 meetings and voted in 0 of 2 votes. Since 3 months ago, gabrielschulhof attended 0 out of 10 meetings and voted in 0 of 2 votes."
  
    commit-message: meta: move one or more TSC members to emeritus
    labels: meta
    title: meta: move one or more TSC members to emeritus
  env:
    NODE_VERSION: lts/*
    INACTIVE_TSC_HANDLES: "@codebytere @gabrielschulhof"
    DETAILS_FOR_COMMIT_BODY: "Since 3 months ago, codebytere attended 0 out of 10 meetings and voted in 0 of 2 votes. Since 3 months ago, gabrielschulhof attended 0 out of 10 meetings and voted in 0 of 2 votes."

The only nit would be to get rid of the " (maybe using fromJSON? not sure); other than that, LGTM.

[Trott]

The only nit would be to get rid of the " (maybe using fromJSON? not sure); other than that, LGTM.

I wonder if spaces aren't a problem in single-line GITHUB_ENV entries and we can just remove the quotation marks there.

[aduh95]

I don't know for GITHUB_ENV, but when using ::set-output quotes are not needed: https://github.com/nodejs/node/pull/40845/files#diff-f9aa500b86b242f58f185509ad323b3526cf5effc683df4b5cb4d78df4108c5fR15-R16

[Trott]

And if all else fails, we can use the multi-line HEREDOC format they support which doesn't require quotation marks or other punctuation around spaces.

[Trott]

(Testing now on my fork.)

[Trott]

Yup, leaving out the quotation marks worked. https://github.com/Trott/io.js/runs/4318829465?check_suite_focus=true (The failure is because I didn't set a needed token on my fork.)

PR coming momentarily.