Added default issue template.

[Viddesh1]

No description provided.

[Viddesh1]

@microsoft-github-policy-service agree

[l-lumin]

I think you should spend some time to modifying the issue templates to suit this repository rather than using the default

[Viddesh1]

Hello @l-lumin ,

Thanks for checking the pull request.

Currently, I am not really sure what would be the best Issue template format for this project.

Below are some of the issue templates that took a glance:-

https://github.com/microsoft/TypeScript/issues/new?template=bug_report.yml
https://github.com/microsoft/vscode/issues/new?template=feature_request.md
https://github.com/microsoft/RD-Agent/issues/new?template=bug-report.md
https://github.com/microsoft/debugpy/issues/new?template=bug_report.md
https://github.com/microsoft/pyright/issues/new?template=bug_report.md

Different repository have either markdown and form based issue template fine tuned to specific requirements for respective projects.

Below are the points thatIi think they have in common which included in the issue template issue and pull request template.

1. https://github.com/microsoft/markitdown/blob/main/README.md
2. https://github.com/microsoft/markitdown/blob/main/SUPPORT.md
3. https://github.com/microsoft/markitdown/blob/main/SECURITY.md
4. https://github.com/microsoft/markitdown/blob/main/CODE_OF_CONDUCT.md
5. Please search existing issues or pull request to avoid creating duplicates.

Regards!
Viddesh

[l-lumin]

I think for the issue templates, we should start with two types:

• for feature requests, such as adding support for a new file format (and maybe including a sample file)
• for bug reports, which should include details like the problem description, steps to reproduce, additional information like the version, and the file

[gagb]

remove smartphone. combine with desktop

[Viddesh1]

Thanks for comment. I removed the smartphone information and removed extra space in between.

[gagb]

Is there a reason you used md instead of YAML? https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

We should keep the issue template really concise.

[Viddesh1]

Hello @gagb ,

The reason is simplicity.
Markdown provides simplicity to us to update issue template and issue creator using md template to update the issue or feature request. Also, if they want they can update the template specific to creating the issues add or subtract specific information.

YAML form based issue templates is also good. Since it is form based issue creator can add the specific information that they want in specific form based fields. It would also make sure that all the fields are filled with some information and no fields are empty. If we want concise information then we can go with YAML.

Which one do you prefer?

Thanks!
Viddesh