You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should we replace the seemingly unmaintained https://github.com/xt0rted/slash-command-action (last updated in 2022) with a different one, such as https://github.com/peter-evans/slash-command-dispatch, as our slash commands processing action? This will squash some node16 deprecation notices from GitHub Actions outputs.
Any extra information?
The current slash commands processor we are using is causing GitHub Actions to emit node16 actions deprecation messages. The project was last updated in 2022, and issues and PRs in the repository are going unanswered. It might be prudent to move to a different action.
The text was updated successfully, but these errors were encountered:
What changes would you like?
Should we replace the seemingly unmaintained
https://github.com/xt0rted/slash-command-action
(last updated in 2022) with a different one, such ashttps://github.com/peter-evans/slash-command-dispatch
, as our slash commands processing action? This will squash some node16 deprecation notices from GitHub Actions outputs.Any extra information?
The current slash commands processor we are using is causing GitHub Actions to emit node16 actions deprecation messages. The project was last updated in 2022, and issues and PRs in the repository are going unanswered. It might be prudent to move to a different action.
The text was updated successfully, but these errors were encountered: