Update Github issue templates to use issue forms

[msulprizio]

Name and Institution (Required)

Name: Melissa Sulprizio
Institution: Harvard

Describe the update

Github issue template files are updated to utilize issue forms. This involves using YAML configuration files instead of markdown. This should make issue submissions easier for users and will ensure users provide the required information.

Note that issue forms are not supported for pull requests currently.

Expected changes

This is a zero difference update to model output. It will only impact the look of submitting issues on Github once merged into the main branch.

Related Github Issue(s)

• Closes [FEATURE REQUEST] Use yml and incorporate other form elements in issue templates #1831
• Update Github issue templates to use issue forms HEMCO#276
• Update Github issue templates to use issue forms GCClassic#58
• Update Github issue templates to use issue forms GCHP#415

[msulprizio]

A temporary repository has been set up at https://github.com/msulprizio/test_issues_form/issues/new/choose for testing these new forms without merging into main here.

[yantosca]

Thanks @msulprizio. This looks great overall, I've just noted a few minor things.

[lizziel]

This looks great for GC-Classic issues. I wonder if we should have a drop-down for what simulation, e.g. fullchem, and configuration, e.g. GC-Classic nested, they are using. Sometimes GCHP users create issues on GEOS-Chem repo but there is no place for them to say they are using GCHP.

[yantosca]

Thanks for the updates @msulprizio! Good to merge, pending @lizziel's additional comments

[msulprizio]

I wonder if we should have a drop-down for what simulation, e.g. fullchem, and configuration, e.g. GC-Classic nested, they are using. Sometimes GCHP users create issues on GEOS-Chem repo but there is no place for them to say they are using GCHP.

@lizziel That's a good point! I added additional entries to the form for configuration, simulation type, resolution, and met field.

Let me know if you think anything else should be added/changed!

[yantosca]

@lizziel @msulprizio, this looks great!

[lizziel]

Looks good! A few more comments:

• If using GCHP then users should also provide MPI library and version
• If we include CESM and WRF-GC then we should also include GEOS
• I'm hesitant to start down the path of asking for libraries and config files for GEOS-Chem in external models. GCHP run issues should be in the GCHP github, and GEOS-Chem in GEOS issues go to the GMAO github, and CESM issues go to the CESM user forum. I don't think we give WRF-GC help either. I wonder if we should add a note pointing people to those resources?

[lizziel]

Thinking more about this, I can see GMAO developers making an issue (although right now they just ping me on their own github issues) and NCAR developers too if they have a question or something breaks. But I still wonder if we should list other resources somewhere such as GCHP GitHub for GCHP issues, or explain GEOS-Chem repo issues are for all GC-Classic issues plus science codebase issues if run in GCHP or other models.

[msulprizio]

@lizziel I removed the options related to external models from the configuration question and added a note for users to check with the external model's support.