From a840fe12f1e45a03eba1fc1e943abfd486e363c4 Mon Sep 17 00:00:00 2001 From: Tapawingo Date: Wed, 3 Jan 2024 21:23:27 +0100 Subject: [PATCH 1/4] Added new form --- .github/ISSUE_TEMPLATE/bug_report.md | 53 ----------------- .github/ISSUE_TEMPLATE/bug_report.yml | 85 +++++++++++++++++++++++++++ 2 files changed, 85 insertions(+), 53 deletions(-) delete mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/ISSUE_TEMPLATE/bug_report.yml diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md deleted file mode 100644 index 68b93a4..0000000 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -name: Bug report -about: Create a report to help us improve -title: '' -labels: '' -assignees: '' - ---- - - - -**Version:** -- **CMF3:** `3.x.x` [e.g. 3.0.0 stable, commit hash] - -**Description:** -A clear and concise description of what the bug is. - -**Steps to reproduce:** -_Follow [this flowchart](https://wiki.cluster-community.com/index.php/CMF3:_Issue_Flowchart)!_ - -1. _Go to ..._ -2. _Click ..._ -3. _See ..._ - -**Expected behavior:** -A clear and concise description of what you expected to happen. - -**Where did the issue occur?** -- Dedicated / Self-Hosted Multiplayer / Singleplayer / Editor (Singleplayer) / Editor (Multiplayer) - -**Log Files:** -- Link to ([gist](https://gist.github.com) or [pastebin](http://pastebin.com)) to the client and/or server RPT file. An instruction to find your RPT files can be found [here](https://community.bistudio.com/wiki/Crash_Files#Arma_3). - -**Mission Files:** -If you have access to the mission file add it here. - -**Additional context:** -Add any other context about the problem here. - -**Screenshots:** -If applicable, add screenshots to help explain your problem. diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml new file mode 100644 index 0000000..d2944ca --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -0,0 +1,85 @@ +name: Bug Report +description: Create a report to help us improve +title: "" +labels: ["kind/bug"] +body: + - type: markdown + attributes: + value: Thank you for taking the time to report a bug with our Framework. + - type: checkboxes + attributes: + label: I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING + options: + - label: If I delete this entire template or parts of it and go my own path, the team may close my issue without further explanation or engagement. + required: true + - label: If I list multiple bugs/concerns in this one issue, the team may close my issue without further explanation or engagement. + required: true + - label: If I write an issue that has duplicates, the team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). + required: true + - label: If I leave the title incomplete when filing the issue, the team may close my issue without further explanation or engagement. + required: true + - label: If I file something completely blank in the body, the team may close my issue without further explanation or engagement. + required: true + - label: If I file an issue without collecting logs (RPT file, etc...), the team may close my issue without further explanation or engagement. + required: true + - type: dropdown + id: version + attributes: + label: Version + description: What version of CMF3 are you running? + options: + - v1.0.0 + - v1.1.0 + - v2.0.0-RC1 + - v2.0.0 + - v2.1.0 + - v2.1.1-dev + - type: textarea + id: description + attributes: + label: Description + description: A clear and concise description of what the bug is. + - type: textarea + id: steps + attributes: + label: Steps to reproduce + description: _Follow [this flowchart](https://wiki.cluster-community.com/index.php/CMF3:_Issue_Flowchart)!_ + placeholder: "1. _Go to ..._ +2. _Click ..._ +3. _See ..._" + - type: textarea + id: expected + attributes: + label: Expected behavior + description: A clear and concise description of what you expected to happen. + - type: checkboxes + id: environment + attributes: + label: Where did the issue occur? + options: + - label: Dedicated + - label: Self-Hosted Multiplayer + - label: Singleplayer + - label: Editor (Singleplayer) + - label: Editor (Multiplayer) + - label: Editor + - type: input + id: logfiles + attributes: + label: Log Files + description: Link to ([gist](https://gist.github.com) or [pastebin](http://pastebin.com)) to the client and/or server RPT file. An instruction to find your RPT files can be found [here](https://community.bistudio.com/wiki/Crash_Files#Arma_3). + - type: input + id: missionfiles + attributes: + label: Mission Files + description: If you have access to the mission file add it here. + - type: textarea + id: additionalContext + attributes: + label: Additional Context + description: Add any other context about the problem here. + - type: textarea + id: screenshots + attributes: + label: Screenshots + description: If applicable, add screenshots to help explain your problem. \ No newline at end of file From ef72ba0d9909bcafb6351c6b9835e5dd0da61256 Mon Sep 17 00:00:00 2001 From: Tapawingo <60672612+Tapawingo@users.noreply.github.com> Date: Wed, 3 Jan 2024 21:26:11 +0100 Subject: [PATCH 2/4] Fixed issues with bug_report.yml --- .github/ISSUE_TEMPLATE/bug_report.yml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index d2944ca..1e3789d 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -1,6 +1,5 @@ name: Bug Report description: Create a report to help us improve -title: "" labels: ["kind/bug"] body: - type: markdown @@ -82,4 +81,4 @@ body: id: screenshots attributes: label: Screenshots - description: If applicable, add screenshots to help explain your problem. \ No newline at end of file + description: If applicable, add screenshots to help explain your problem. From c38eff77e38e2cbc1dee6b280a69d89fa2be736f Mon Sep 17 00:00:00 2001 From: Tapawingo Date: Wed, 3 Jan 2024 21:33:37 +0100 Subject: [PATCH 3/4] Updated feature_request --- .github/ISSUE_TEMPLATE/feature_request.md | 24 -------------------- .github/ISSUE_TEMPLATE/feature_request.yml | 26 ++++++++++++++++++++++ 2 files changed, 26 insertions(+), 24 deletions(-) delete mode 100644 .github/ISSUE_TEMPLATE/feature_request.md create mode 100644 .github/ISSUE_TEMPLATE/feature_request.yml diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md deleted file mode 100644 index 6e08393..0000000 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -name: Feature request -about: Suggest an idea for this project -title: '' -labels: '' -assignees: '' - ---- - - - -**Description of feature:** -A clear and concise description of the feature. diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml new file mode 100644 index 0000000..bd5079e --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -0,0 +1,26 @@ +name: Feature Request +description: Suggest an idea for this project +labels: ["kind/Feature Request"] +body: + - type: markdown + attributes: + value: Thank you for taking the time to report a bug with our Framework. + - type: checkboxes + attributes: + label: I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING + options: + - label: If I delete this entire template or parts of it and go my own path, the team may close my issue without further explanation or engagement. + required: true + - label: If I list multiple features in this one issue, the team may close my issue without further explanation or engagement. + required: true + - label: If I write a feature that has duplicates, the team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). + required: true + - label: If I leave the title incomplete when filing the request, the team may close my issue without further explanation or engagement. + required: true + - label: If I file something completely blank in the body, the team may close my issue without further explanation or engagement. + required: true + - type: textarea + id: description + attributes: + label: Description of Feature + description: A clear and concise description of the feature. \ No newline at end of file From db4e91e19afec70e5a993a3dc9ce6de418c4a193 Mon Sep 17 00:00:00 2001 From: Tapawingo Date: Wed, 3 Jan 2024 21:34:26 +0100 Subject: [PATCH 4/4] Fixed issue with feature_request.yml --- .github/ISSUE_TEMPLATE/feature_request.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml index bd5079e..126287a 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.yml +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -1,6 +1,6 @@ name: Feature Request description: Suggest an idea for this project -labels: ["kind/Feature Request"] +labels: ["kind/feature request"] body: - type: markdown attributes: