Add standardized issue templates for feature requests and bug reports

[DevTwilight]

Description

I would like to propose adding structured issue templates for Bug Reports and Feature Requests to make issues easier to understand, triage, and maintain.

Currently, issues have different formats depending on the reporter. A consistent template could help contributors provide the necessary information upfront and make discussions more efficient.

This is only a proposal for discussion before implementation.

@NathanLovato

Current situation

Some recent issues already contain useful information, but the structure differs.

Example bug report sections:

• Description
• Reproduce
• Expected behaviour
• Observed behaviour
• Additional informations

Example feature request sections:

• Proposal
• Motivation
• Discussion
• Alternatives / considerations

These formats work well, but having a standard template would make future issues more consistent.

Proposed change

Add GitHub issue templates:

Bug Report

Suggested sections:

• Description
• Environment
  • GDScript formatter version
  • Godot version
  • Operating system
• Steps to reproduce
• Expected behaviour
• Actual behaviour
• Minimal reproduction example
• Additional information

Feature Request

Suggested sections:

• Description
• Motivation / use case
• Proposed solution
• Alternatives considered
• Additional context

Benefits

• Easier issue triage
• Better reproduction information for bugs
• More complete feature discussions
• More consistent contributor experience

Discussion

Before implementing this, I would like to get feedback:

• Which fields should be required?
• Should templates stay minimal or include more guidance?
• Are there existing workflows that templates should respect?

Related discussions

Examples of detailed issues that inspired this proposal:

• Bug reports with reproduction steps and environment details
• Feature requests with design discussion and alternatives

[NathanLovato]

Thanks for the thought but that I'm not too interested in for this repository. The verbosity adds more burden than it helps, especially when people feed this templates to LLMs to fill like some contributors do. It's seemingly more detailed but actually just more info to ignore. Templates generally nudge people toward having to come up with justification they don't need to give me.

What's most valuable to me is generally people staying available to have a short exchange in the occasional cases more info is needed and everyone being understanding and patient

[DevTwilight]

Thanks for the feedback, Nathan. I understand the concern about making issues too structured and adding unnecessary overhead for contributors.
I agree that keeping the process lightweight can be more effective
Thanks for taking the time to share your perspective.