Skip to content

Commit 67d5dbc

Browse files
forsyth2forsyth2
authored
Update Github templates (#514)
1 parent 54aa0a2 commit 67d5dbc

File tree

3 files changed

+33
-33
lines changed

3 files changed

+33
-33
lines changed

‎.github/DISCUSSION_TEMPLATE/questions.yml‎

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ body:
3939
attributes:
4040
label: What machine were you running on?
4141
description: |
42-
List the machine(s) you encounter the issue on (e.g., Chrysalis, Compy, Perlmutter).
42+
List the machine(s) you encounter the issue on (e.g., Chrysalis, Compy, Perlmutter).
4343
validations:
4444
required: true
4545

@@ -56,38 +56,38 @@ body:
5656
id: zppy-command
5757
attributes:
5858
label: What command did you run?
59-
description: |
60-
Copy the command causing the issue (e.g., `zppy -c tests/integration/generated/test_complete_run_chrysalis.cfg`). This will be automatically formatted into code, so no need for markdown backticks.
61-
render: bash
59+
description: |
60+
Copy the command causing the issue (e.g., `zppy -c tests/integration/generated/test_complete_run_chrysalis.cfg`). This will be automatically formatted into code, so no need for markdown backticks.
61+
render: bash
6262
validations:
6363
required: true
6464

6565
- type: textarea
6666
id: cfg-file
6767
attributes:
6868
label: Copy your cfg file
69-
description: |
70-
Copy the contents of your cfg file into the space below. This will be automatically formatted into code, so no need for markdown backticks.
71-
render: bash
69+
description: |
70+
Copy the contents of your cfg file into the space below. This will be automatically formatted into code, so no need for markdown backticks.
71+
render: bash
7272
validations:
7373
required: true
7474

7575
- type: textarea
7676
id: status-output
7777
attributes:
7878
label: What jobs are failing?
79-
description: |
80-
Go to the `output` line of your cfg. `cd` into `post/scripts`. Copy the output of `grep -v "OK" *status`. This will be automatically formatted into code, so no need for markdown backticks.
81-
render: bash
79+
description: |
80+
Go to the `output` line of your cfg. `cd` into `post/scripts`. Copy the output of `grep -v "OK" *status`. This will be automatically formatted into code, so no need for markdown backticks.
81+
render: bash
8282
validations:
8383
required: false
8484

8585
- type: textarea
8686
id: stack-trace
8787
attributes:
8888
label: What stack trace are you encountering?
89-
description: |
90-
Copy a stack trace from one of your failing jobs. This will be automatically formatted into code, so no need for markdown backticks.
91-
render: bash
89+
description: |
90+
Copy a stack trace from one of your failing jobs. This will be automatically formatted into code, so no need for markdown backticks.
91+
render: bash
9292
validations:
9393
required: false

‎.github/ISSUE_TEMPLATE/bug_report.yml‎

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ body:
1919
attributes:
2020
label: What machine were you running on?
2121
description: |
22-
List the machine(s) you encounter the issue on (e.g., Chrysalis, Compy, Perlmutter).
22+
List the machine(s) you encounter the issue on (e.g., Chrysalis, Compy, Perlmutter).
2323
validations:
2424
required: true
2525

@@ -36,38 +36,38 @@ body:
3636
id: zppy-command
3737
attributes:
3838
label: What command did you run?
39-
description: |
40-
Copy the command causing the issue (e.g., `zppy -c tests/integration/generated/test_complete_run_chrysalis.cfg`). This will be automatically formatted into code, so no need for markdown backticks.
41-
render: bash
39+
description: |
40+
Copy the command causing the issue (e.g., `zppy -c tests/integration/generated/test_complete_run_chrysalis.cfg`). This will be automatically formatted into code, so no need for markdown backticks.
41+
render: bash
4242
validations:
4343
required: true
4444

4545
- type: textarea
4646
id: cfg-file
4747
attributes:
4848
label: Copy your cfg file
49-
description: |
50-
Copy the contents of your cfg file into the space below. This will be automatically formatted into code, so no need for markdown backticks.
51-
render: bash
49+
description: |
50+
Copy the contents of your cfg file into the space below. This will be automatically formatted into code, so no need for markdown backticks.
51+
render: bash
5252
validations:
5353
required: true
5454

5555
- type: textarea
5656
id: status-output
5757
attributes:
5858
label: What jobs are failing?
59-
description: |
60-
Go to the `output` line of your cfg. `cd` into `post/scripts`. Copy the output of `grep -v "OK" *status`. This will be automatically formatted into code, so no need for markdown backticks.
61-
render: bash
59+
description: |
60+
Go to the `output` line of your cfg. `cd` into `post/scripts`. Copy the output of `grep -v "OK" *status`. This will be automatically formatted into code, so no need for markdown backticks.
61+
render: bash
6262
validations:
6363
required: false
6464

6565
- type: textarea
6666
id: stack-trace
6767
attributes:
6868
label: What stack trace are you encountering?
69-
description: |
70-
Copy a stack trace from one of your failing jobs. This will be automatically formatted into code, so no need for markdown backticks.
71-
render: bash
69+
description: |
70+
Copy a stack trace from one of your failing jobs. This will be automatically formatted into code, so no need for markdown backticks.
71+
render: bash
7272
validations:
7373
required: false

‎.github/ISSUE_TEMPLATE/feature_request.yml‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,13 +9,13 @@ body:
99
attributes:
1010
label: How will this affect the next version number?
1111
description: |
12-
`zppy` uses semantic versioning (https://semver.org/). Bug fixes and small improvements will increment the PATCH version. New features will increment the MINOR version. Incompatible API changes will increment the MAJOR version. The amount of work required to implement a request typically increases with each level. (For bug fixes, use the "Bug Report" template).
13-
multiple: false
14-
options:
15-
- Small improvement (increment PATCH version)
16-
- New feature (increment MINOR version)
17-
- Incompatibile API change (increment MAJOR version)
18-
default: 1
12+
`zppy` uses semantic versioning (https://semver.org/). Bug fixes and small improvements will increment the PATCH version. New features will increment the MINOR version. Incompatible API changes will increment the MAJOR version. The amount of work required to implement a request typically increases with each level. (For bug fixes, use the "Bug Report" template).
13+
multiple: false
14+
options:
15+
- Small improvement (increment PATCH version)
16+
- New feature (increment MINOR version)
17+
- Incompatibile API change (increment MAJOR version)
18+
default: 1
1919
validations:
2020
required: true
2121

0 commit comments

Comments
 (0)