-
Notifications
You must be signed in to change notification settings - Fork 38
New templates for issues #1017
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
New templates for issues #1017
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
name: Bug Report | ||
description: Report a bug related to WeatherGenerator. | ||
labels: ["bug"] | ||
body: | ||
- type: textarea | ||
id: what-happened | ||
attributes: | ||
label: What happened? | ||
description: | | ||
Actual Results: What happened when you got the bug? | ||
Expected Results: What was supposed to happen? | ||
Additional Information: Add anything else you feel we need to know e.g. The exact error message printed | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: reproduce | ||
attributes: | ||
label: What are the steps to reproduce the bug? | ||
description: | | ||
Minimal steps to reproduce the behavior: | ||
- code branch with ALL configuration files | ||
- HPC | ||
- run_id | ||
- command run | ||
- if applicable: node configuration | ||
validations: | ||
required: "false" | ||
- type: input | ||
id: data | ||
attributes: | ||
label: Hedgedoc link to logs and more information. This ticket is public, do not attach files directly. | ||
description: Please put all relevant information (logs, plots, etc.) in the Hedgedoc and link it here. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
name: Initiative | ||
description: A piece of work that will likely take more than a week to complete. | ||
title: "[ISSUE] " | ||
labels: ["initiative"] | ||
|
||
body: | ||
- type: markdown | ||
attributes: | ||
value: | | ||
Describe the task. It can be a feature, documentation, etc. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "It can be a feature, documentation, etc." -> "It can be a feature, a set of experiments, documentation, etc." |
||
|
||
Be specific and provide context. | ||
|
||
Tips for writing good initiatives: | ||
https://gitlab.jsc.fz-juelich.de/esde/WeatherGenerator-private/-/wikis/Design-docs/Writing-a-design-doc | ||
|
||
- type: input | ||
id: hedgedoc_url | ||
attributes: | ||
label: Hedgedoc URL, if you are keeping notes, plots, logs in hedgedoc. | ||
description: Hedgedoc URL, if you are keeping notes, plots, logs in hedgedoc. | ||
placeholder: "https://gitlab.jsc.fz-juelich.de/hedgedoc/..." | ||
validations: | ||
required: false | ||
|
||
|
||
- type: input | ||
id: design_url | ||
attributes: | ||
label: URL to the design document | ||
description: Paste a link to logs, screenshots, or related resources | ||
placeholder: "" | ||
validations: | ||
required: false | ||
|
||
|
||
- type: checkboxes | ||
id: area | ||
attributes: | ||
label: Area | ||
description: The general area this task relates to. | ||
options: | ||
- label: datasets, data readers, data preparation and transfer | ||
- label: model | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
- label: infrastructure and engineering | ||
- label: evaluation, export and visualization | ||
- label: documentation | ||
validations: | ||
required: true | ||
|
||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
name: Task / Issue | ||
description: A task or issue that should take less than a week to complete. | ||
title: "[ISSUE] " | ||
|
||
body: | ||
- type: markdown | ||
attributes: | ||
value: | | ||
Describe the task. It can be a feature, documentation, etc. | ||
|
||
Be specific and provide context. | ||
|
||
- type: input | ||
id: hedgedoc_url | ||
attributes: | ||
label: Hedgedoc URL, if you are keeping notes, plots, logs in hedgedoc. | ||
description: Paste a link to logs, screenshots, or related resources | ||
placeholder: "https://gitlab.jsc.fz-juelich.de/hedgedoc/..." | ||
validations: | ||
required: false | ||
|
||
- type: checkboxes | ||
id: area | ||
attributes: | ||
label: Area | ||
description: The general area this task relates to. | ||
options: | ||
- label: datasets, data readers, data preparation and transfer | ||
- label: model | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We could again add science here although I have less strong feeling here than for initative |
||
- label: infrastructure and engineering | ||
- label: evaluation, export and visualization | ||
- label: documentation | ||
validations: | ||
required: true | ||
|
||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would switch l10 and 11. For "actual results" I would also talk about "behaviour" and not "results" and "What happened when you got the bug?" -> "What happened instead?|