dessant / support-requests Goto Github PK

Using this action generates warnings:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: dessant/support-requests@v2. [...]

Example

Hi!

Support Requests has been rewritten for GitHub Actions, offering new features and better control over your automation presets. The legacy GitHub App has been deprecated, and the public instance of the app has been shut down. You're receiving this message because the deprecated app is still installed for your user account or organization.

You can follow the user guide and examples to install the new action for your repositories:

https://github.com/dessant/support-requests

If you need any help with configuring the action, please open an issue or message me at [email protected].

The continued development of Support Requests is made possible thanks to the support of awesome backers. If you'd like to join them, please check out https://github.com/sponsors/dessant

Please ignore the new permission request for the app, it was only used to notify project maintainers directly, without opening thousands of issues.

Thanks,
Armin Sebastian

Look at MinecraftForge/MinecraftForge#5383

For some reason, support bot fails to close this issue. Was support bot down when the issue was marked?

Hey @dessant, this app looks great! Would you be interested in having this listed on probot.github.io? Here are the directions for submitting it to the site if you're interested.

Would it be possible, to somehow add multi-label support for this bot?

I imagine it like this, where you have a labels folder inside the .github folder.
And in that labels-folders would be the support.yml, just with the difference, that

1. The filename is the name of the actual label and
2. The file doesn't have the label-name option in it since the filename is the label name.

The bot would then just check the labels folder for any file that has the name of the label and if it finds one, does the actions defined in that file.

That bot is really interesting for me to use, but since I can only have one label set and also have no experience in js, I can't make it myself.
I can understand if that isn't possible.

This is a similar but more specific request than #2 and #3. I have a need for a feature-request bot, which does exactly what this bot does only with the label feature and a different message.

It could be implemented as a multi-label bot, but it could also be a clone of this bot with minor changes.

Reaching out here as a suggestion rather than just doing it myself, because in #2 (comment) you suggest you'd like to create more bots 😄

GitHub supports (manually) closing an issue as either Complete or Not Planned. I assume, without checking, that it permits the same programmatically.

This GitHub action closes the items as Complete. I think Not Planned is a better fit.

I can't see how this makes any practical difference in the real world, apart from signalling a message to users, so please treat this as low priority.

Hey @dessant The bot looks good.

I was wondering what you think about adding support for multiple labels + responses.

The use case I'm thinking of is having the bot add a helpful comment on things and a link to some documentation for issues/PRs that need help. Like: needs-tests, needs-sample-data.

Do you think that would be great or out of scope for your bot?