Refactor Issue Command

Currently the issue command takes a title parameter (for the title of the issue to create), then responds with a prompt for the repository to create the issue on.

The problem with this command is that it bypasses the Issue Template selection screen (which is why my issue isn’t linked to a template).

I propose that the command be refactored to only take a repository, and return the link to the /issues/new/choose endpoint (which leads to the template selection, or to the new blank issue if a repository does not have defined templates).

[stemount]

That is a shame @nhcarrigan - good shout - this does improve the quality of issues, this is a valid enhancement and not something I thought much about in #227

Issue Grooming

1. Can we set a default issue template to fix this problem? (e.g. the bot needs no code changes)…
2. I notice that we could actually respond something better:

https://github.com/EddieJaoudeCommunity/EddieBot/issues/new?template=**bug.md**&title=Bot Is Borked

<stemount> ^issue Bot Is Borked

<EddieBotDev>

To which repository would you like to create an issue?

<stemount> eddiebot

<EddieBotDev>

We found **EddieJaoudeCommunity/EddieBot**:

You create an issue with templates:

BUG issue to  by clicking here <BUG.md URL>.
FEATURE issue to EddieJaoudeCommunity/EddieBot by clicking here <FEATURE.md URL>.

###### Our bot is Open Source, you can find it here https://github.com/EddieJaoudeCommunity/EddieBot

Technical Triage if accepted:-

• Method to look at repositories `.github/ISSUE_TEMPLATE(s) e.g. https://github.com/EddieJaoudeCommunity/EddieBot/tree/develop/.github/ISSUE_TEMPLATE
• Write concise copy on why templates are used
• Support repositories that do not have issue templates
• Decide if we should affix to the querystring of the URL label=bug for bugs as this is what GitHub usually accepts as the “bug” type… and similar types too.

[github-actions[bot]]

Stale issue message