weyne/dcs-retribution
1
0
Fork 0
mirror of https://github.com/dcs-retribution/dcs-retribution.git synced 2025-11-10 15:41:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Issue templates

Browse Source
This commit is contained in:
Raffson 2022-09-25 19:11:50 +02:00
parent ae0cbc2c5b
commit 0a335d342a
No known key found for this signature in database
GPG Key ID: B0402B2C9B764D99
2 changed files with 22 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -17,7 +17,7 @@ body:
label: Affected versions label: Affected versions
multiple: true multiple: true
description: > description: >
Select all DCS Liberation versions in which you have observed this bug. Select all DCS Retribution versions in which you have observed this bug.
You do not need to test all of them, but the information is useful if You do not need to test all of them, but the information is useful if
you have it. you have it.
@ -28,15 +28,16 @@ body:
filing. filing.
If the bug was found in a development build, select "Development build" If the bug was found in a test/development build, select "Test build" or "Development build"
and provide a link to the build in the field below. and provide a link to the applicable build in the field below.
options: options:
- 5.2.0 - 1.0.0
- Test build
- Development build - Development build
- type: input - type: input
attributes: attributes:
label: Development build label: Test/Development build
description: A link to the development build, if applicable. description: A link to the test/development build, if applicable.
- type: textarea - type: textarea
attributes: attributes:
label: Description label: Description
@ -52,27 +53,27 @@ body:
description: > description: >
Attach any files needed to reproduce the bug here. **A save game is Attach any files needed to reproduce the bug here. **A save game is
required.** We typically cannot help without a save game (the required.** We typically cannot help without a save game (the
`.liberation` file found in `.retribution` file found in
`%USERPROFILE%/Saved Games/DCS/Liberation/Saves`), so most bugs filed `%USERPROFILE%/Saved Games/DCS/Retribution/Saves`), so most bugs filed
without saved games will be closed without investigation. without saved games will be closed without investigation.
Other useful files to include are: Other useful files to include are:
The Liberation log file. The log file is located at The Retribution log file. The log file is located at
`<Liberation install directory>/logs/liberation.log`. The log often `<Retribution install directory>/logs/retribution.log`. The log often
includes data about non-fatal errors that could be the root cause of the includes data about non-fatal errors that could be the root cause of the
problem. problem.
The `liberation_nextturn.miz` or a track file. This should always be The `retribution_nextturn.miz` or a track file. This should always be
included for bugs where the mission was generated incorrectly or where included for bugs where the mission was generated incorrectly or where
the in-game AI is misbehaving. the in-game AI is misbehaving.
The `state.json` file for the most recently completed turn, located at The `state.json` file for the most recently completed turn, located at
`<Liberation install directory>/state.json`. This file is essential for `<Retribution install directory>/state.json`. This file is essential for
investigating any issues with end-of-turn results processing. investigating any issues with end-of-turn results processing.

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

@ -25,7 +25,7 @@ body:
label: Affected versions label: Affected versions
multiple: true multiple: true
description: > description: >
Select all DCS Liberation versions in which you have observed this bug. Select all DCS Retribution versions in which you have observed this bug.
You do not need to test all of them, but the information is useful if You do not need to test all of them, but the information is useful if
you have it. you have it.
@ -36,15 +36,16 @@ body:
filing. filing.
If the bug was found in a development build, select "Development build" If the bug was found in a test/development build, select "Test build" or "Development build"
and provide a link to the build in the field below. and provide a link to the applicable build in the field below.
options: options:
- 5.2.0 - 1.0.0
- Test build
- Development build - Development build
- type: input - type: input
attributes: attributes:
label: Development build label: Test/Development build
description: A link to the development build, if applicable. description: A link to the test/development build, if applicable.
- type: input - type: input
attributes: attributes:
label: Campaign name label: Campaign name
@ -102,8 +103,8 @@ body:
attributes: attributes:
label: Log file label: Log file
description: > description: >
Attach the Liberation log file. The log file is located at Attach the Retribution log file. The log file is located at
`<Liberation install directory>/logs/liberation.log`. `<Retribution install directory>/logs/retribution.log`.
You can attach files to the bug by dragging and dropping the file You can attach files to the bug by dragging and dropping the file