Github issue triage #356
Description
There is already an issue-comment.yml Github action that uses mycoder to respond to user comments. I would like to add another mycoder automation to this repository. This time I would like to have a new issue triage workflow, issue-created.yml. And it should use guidelines in a file located in .mycoder/ISSUE_TRIAGE.md.
It should set the type of the issue: Bug, Feature, Request.
It should tag the issue as well: as bug, documentation, question, duplicate (if it is a duplicate, a comment should be added to link to the duplicate issue), enhancement, help wanted.
If the issue is too vague, mycoder should ask for more information.
If the issue is a bug, try to do a cursory investigation to see what could be the cause and post it back as a comment. If the issue is an enhancement, do a cursory investigation to suggest how it could be realized. If the issue is a question, see if you can answer the question based on researching the code and documentation. Basically try to be helpful and to move the reported issue towards a resolution.
These guidelines should be in the ISSUE_TRIAGE.md file. The GitHub action should be as minimal as possible, based on the existing issue-comment.yml file, with the main instructions in ISSUE_TRIAGE.md so that the behavior can be easily modified over time by non-technical users.