Skip to content

Update issue templates#1225

Merged
davegill merged 1 commit intorelease-v4.2.1from
davegill-patch-1
Jul 9, 2020
Merged

Update issue templates#1225
davegill merged 1 commit intorelease-v4.2.1from
davegill-patch-1

Conversation

@davegill
Copy link
Contributor

@davegill davegill commented Jun 24, 2020

TYPE: new feature

KEYWORDS: issue template

SOURCE: internal

DESCRIPTION OF CHANGES:
A first cut at setting up a bug-fix template for issues. I'm not really sure what this will look like.

LIST OF MODIFIED FILES:
.github/ISSUE_TEMPLATE/bug_report.md

TESTS CONDUCTED:

  1. Does not impact the build or run of the WRF model, no test required.

@davegill davegill requested a review from a team as a code owner June 24, 2020 02:30
@davegill davegill changed the base branch from master to release-v4.2.1 June 24, 2020 02:30
@davegill
Copy link
Contributor Author

@mgduda @kkeene44 @weiwangncar @smileMchen @dudhia
Folks,
Miles, Michael, and I chatted about this a bit today - trying to get a template for the "issues" for WRF. This is seeing what this could look like for us. Sorry for the atypical PR starting branch, but github sort of did much of this for me.

@weiwangncar
Copy link
Collaborator

@davegill If this file is this hidden, how do you expect people who report issues to find it? How do you want this file to be used?

@davegill
Copy link
Contributor Author

@weiwangncar
I agree with everything you say. We are still working this out. :)

@mgduda
Copy link
Collaborator

mgduda commented Jun 24, 2020

@weiwangncar The file is used by GitHub to provide the default text when someone opens a new Issue. To see how this works, go to https://github.com/mgduda/MPAS-Scratch/issues and try opening a new issue.

@mgduda
Copy link
Collaborator

mgduda commented Jun 24, 2020

@davegill As an alternative to using the GitHub web interface to create Issue templates for "bug reports", etc., it's possible to create a general template by just committing a new file, .github/ISSUE_TEMPLATE.md to the repository. I don't know whether this has to be a commit to the master branch or not.

@weiwangncar
Copy link
Collaborator

@mgduda Thanks. It makes sense if it just pops up when a new issue is opened.

@davegill davegill merged commit c66a806 into release-v4.2.1 Jul 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants