weyne/dcs_liberation
1
0
Fork 0
mirror of https://github.com/dcs-liberation/dcs_liberation.git synced 2025-11-10 14:22:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update bug templates to 6.0.0.

Browse Source 
We're not fixing 5.x bugs any more.
This commit is contained in:
Dan Albert 2022-11-25 15:18:57 -08:00
parent 68fc4f6950
commit ded5fc8b1d
2 changed files with 22 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
.github/ISSUE_TEMPLATE/bug-report.yml vendored
View File

@ -31,12 +31,13 @@ body:
If the bug was found in a development build, select "Development build"
and provide a link to the build in the field below.
options:
- 5.2.0
- 6.0.0
- Development build
- type: textarea
attributes:
label: Build information
description: The build information from the Help -> Report an issue window.
description:
The build information from the Help -> Report an issue window.
- type: textarea
attributes:
label: Description
@ -52,18 +53,17 @@ body:
description: >
Attach any files needed to reproduce the bug here. **A save game is
required.** We typically cannot help without a save game (the
`.liberation` file found in
`%USERPROFILE%/Saved Games/DCS/Liberation/Saves`), so most bugs filed
without saved games will be closed without investigation.
`.liberation` file found in `%USERPROFILE%/Saved
Games/DCS/Liberation/Saves`), so most bugs filed without saved games
will be closed without investigation.
Other useful files to include are:
The Liberation log file. The log file is located at
`<Liberation install directory>/logs/liberation.log`. The log often
includes data about non-fatal errors that could be the root cause of the
problem.
The Liberation log file. The log file is located at `<Liberation install
directory>/logs/liberation.log`. The log often includes data about
non-fatal errors that could be the root cause of the problem.
The `liberation_nextturn.miz` or a track file. This should always be
@ -76,8 +76,8 @@ body:
investigating any issues with end-of-turn results processing.
You can attach files to the bug by dragging and dropping the file
into this text box. GitHub will not allow uploads of all file types, so
You can attach files to the bug by dragging and dropping the file into
this text box. GitHub will not allow uploads of all file types, so
attach a zip of the files if needed.
validations:
required: true

21
.github/ISSUE_TEMPLATE/new-game-bug.yml vendored
View File

@ -39,12 +39,13 @@ body:
If the bug was found in a development build, select "Development build"
and provide a link to the build in the field below.
options:
- 5.2.0
- 6.0.0
- Development build
- type: textarea
attributes:
label: Build information
description: The build information from the Help -> Report an issue window.
description:
The build information from the Help -> Report an issue window.
- type: input
attributes:
label: Campaign name
@ -59,8 +60,8 @@ body:
label: Blue faction
description: >
The name of the blue faction you selected. If the bug only occurs with a
custom faction (or modifications to a stock faction), upload the
faction file as an attachment to the bug description field.
custom faction (or modifications to a stock faction), upload the faction
file as an attachment to the bug description field.
validations:
required: true
- type: input
@ -68,8 +69,8 @@ body:
label: Red faction
description: >
The name of the red faction you selected. If the bug only occurs with a
custom faction (or modifications to a stock faction), upload the
faction file as an attachment to the bug description field.
custom faction (or modifications to a stock faction), upload the faction
file as an attachment to the bug description field.
validations:
required: true
- type: textarea
@ -102,11 +103,11 @@ body:
attributes:
label: Log file
description: >
Attach the Liberation log file. The log file is located at
`<Liberation install directory>/logs/liberation.log`.
Attach the Liberation log file. The log file is located at `<Liberation
install directory>/logs/liberation.log`.
You can attach files to the bug by dragging and dropping the file
into this text box.
You can attach files to the bug by dragging and dropping the file into
this text box.
validations:
required: true