feat(stale): also close discussions

[avivkeller]

Now that this repository is going to be hosting the Node.js discussions, I think it'd be nice to have a stalebot to regulate said discussions.

[avivkeller]

This PR has been open for 7 days with no objections.

Just confirming with @nodejs/actions this external action is okay?

[richardlau]

Just confirming with @nodejs/actions this external action is okay?

cc @nodejs/security-wg

[marco-ippolito]

it doesnt seems very popular https://github.com/steffen-karlsson/stalesweeper 😐 I'd rather use something maintained and with a community

[avivkeller]

I would as well, but I literally could not find a single other action that did this.

Spam

[avivkeller]

Confirming the best course of action here?

👎 No stale bot

👍 Use the 3rd-party stale bot.

I've done a look through of the stale bot and I don't see any issues security-wise. Plus, since it's SHA pinned, we can be sure the content matches our expectations.

❤️ Create a 1st-party stale bot for discussions (like a script for this workflow to call, stored under .github)

For any action, in a worst case scenario, the impact is minimal: the worst thing a potential attacker would be able to do would be editing issues/discussions/PRs in this repository.

[bjohansebas]

cc: @nodejs/issue-triage

[avivkeller]

Bump on my previous question

[viZi67]

Ffj

[avivkeller]

Closing due to inactivity.