Add issue templates

[aguschin]

DVC repo has great issue templates https://github.com/iterative/dvc/issues/new/choose, which could be useful for this repo as well. The one for the bug report has a good structure which helps to frame discussion and reflect steps required to reproduce the issue, output of dvc doctor and such. It would be handy to have similar templates in CML repo.

[DavidGOrtega]

@aguschin I have thought about this however there are also some points to consider.

CML team maintains 4 repos:

• cml
• terraform-provider-iterative
• setup-cml
• setup-dvc

and due to the abroad spectrum of CML I feel that the template might be overwhelming to fill, as a user I hate to fill them when Im reporting a ticket 😆 . Said that I agree that we have one but I would not make it very strict

[dacbd]

I think a template for the cml repo could help direct users to some helpful debugging steps at least for runner that would reduce the back and forth.

For not runner just a note to provide as much of the used workflow as possible?

[casperdcl]

How about forms? Would be an even better upgrade. https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms

However my tuppence is such automation may not be that necessary given how responsive we are to new issues.

Automating issue notifications seems to be higher priority IMO, i.e.:

• many upvotes & still open
• no activity for X months
• p0-critical & no activity for X weeks
• opened by non-@iterative/cml person