Skip to content

Commit c51347b

Browse files
authored
Merge pull request #1824 from forcedotcom/release-5.1.0
RELEASE @W-18394670@ Conducting v5.1.0 release
2 parents 5dee049 + b401ed3 commit c51347b

32 files changed

+2441
-9526
lines changed

.github/ISSUE_TEMPLATE/0-code_analyzer_bug.yml

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ description: Report an issue with a code-analyzer command.
33
title: "[BUG][code-analyzer] <YOUR_TITLE_HERE>"
44
labels: []
55
body:
6-
- type: dropdown
6+
- type: checkboxes
77
attributes:
88
label: Have you tried to resolve this issue yourself first?
99
description: |
@@ -13,15 +13,10 @@ body:
1313
3. Double-check the command that you ran. Ensure that items like file names, method names, and category names are correctly spelled and cased.
1414
4. Verify that your code is syntactically valid.
1515
5. Verify that the error is reproducible on another machine.
16-
6. Check open and closed [issues](https://github.com/forcedotcom/sfdx-scanner/issues) to see if your issue is already logged.
17-
18-
**I confirm that I have gone through these steps and still have an issue to report.**
19-
<sup>(You must select "Yes" to create an issue.)</sup>
16+
6. Check open and closed [issues](https://github.com/forcedotcom/code-analyzer/issues) to see if your issue is already logged.
2017
options:
21-
- ''
22-
- "Yes"
23-
validations:
24-
required: true
18+
- label: I confirm I have gone through the above steps and still have an issue to report
19+
required: true
2520
- type: textarea
2621
attributes:
2722
label: Bug Description
Lines changed: 114 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
name: Report a Bug with a scanner command (v4)
2+
description: Report an issue with a scanner command.
3+
title: "[BUG][scanner] <YOUR_TITLE_HERE>"
4+
labels: []
5+
body:
6+
- type: checkboxes
7+
attributes:
8+
label: Have you tried to resolve this issue yourself first?
9+
description: |
10+
Oftentimes, you can resolve `scanner` issues on your own. Follow these steps:
11+
1. Read the error message.
12+
2. Read [Salesforce Code Analyzer](https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/overview) documentation.
13+
3. Double-check the command that you ran. Ensure that items like file names, method names, and category names are correctly spelled and cased.
14+
4. Verify that your code is syntactically valid.
15+
5. Verify that the error is reproducible on another machine.
16+
6. Check open and closed [issues](https://github.com/forcedotcom/code-analyzer/issues) to see if your issue is already logged.
17+
options:
18+
- label: I confirm I have gone through the above steps and still have an issue to report
19+
required: true
20+
- type: textarea
21+
attributes:
22+
label: Bug Description
23+
description: Provide a clear and concise description of what the bug is and include the exact command that you ran.
24+
validations:
25+
required: true
26+
- type: textarea
27+
attributes:
28+
label: Output / Logs
29+
description: Attach any output or logs here
30+
placeholder: |
31+
Add log output here or drag files here.
32+
- type: textarea
33+
attributes:
34+
label: Steps To Reproduce
35+
description: List out the steps that you used to reproduce the bug behavior. Be as specific and clear as possible.
36+
placeholder: |
37+
1. I first do ...
38+
2. Then I do ...
39+
3. Lastly, I do ...
40+
validations:
41+
required: true
42+
- type: textarea
43+
attributes:
44+
label: Expected Behavior
45+
description: Provide a clear and concise description of what you expected to happen.
46+
validations:
47+
required: true
48+
- type: input
49+
attributes:
50+
label: Operating System
51+
description: |
52+
What is your machine's operating system?
53+
placeholder: |
54+
Example: MacOS Sonoma 14.4.1
55+
validations:
56+
required: true
57+
- type: input
58+
attributes:
59+
label: Salesforce CLI Version
60+
description: |
61+
What do you get from the command "sf --version"?
62+
placeholder: |
63+
Example: @salesforce/cli/2.40.7 darwin-arm64 node-v20.12.2
64+
validations:
65+
required: true
66+
- type: input
67+
attributes:
68+
label: Scanner Plugin Version
69+
description: |
70+
What do you get from the command "sf plugins"?
71+
placeholder: |
72+
Example: @salesforce/sfdx-scanner/4.10.0
73+
validations:
74+
required: true
75+
- type: input
76+
attributes:
77+
label: Node Version
78+
description: |
79+
What do you get from the command "node --version"?
80+
placeholder: |
81+
Example: v23.4.0
82+
validations:
83+
required: false
84+
- type: input
85+
attributes:
86+
label: Java Version
87+
description: |
88+
What do you get from the command "java -version"?
89+
placeholder: |
90+
Example: openjdk version "11.0.17.0.1" 2022-10-18 LTS
91+
validations:
92+
required: false
93+
- type: textarea
94+
attributes:
95+
label: Additional Context (Screenshots, Files, etc)
96+
description: Add any other context about the problem.
97+
placeholder: |
98+
Drag any files or screenshots you have here.
99+
- type: textarea
100+
attributes:
101+
label: Workaround
102+
description: What ways have you found to sidestep the problem? If you haven't found a workaround, what have you tried so far?
103+
- type: dropdown
104+
attributes:
105+
label: Urgency
106+
description: What is the severity of the problem?
107+
options:
108+
- Low
109+
- Moderate
110+
- High
111+
- Critical
112+
default: 0
113+
validations:
114+
required: true

.github/ISSUE_TEMPLATE/1-scanner_run_bug.yml

Lines changed: 0 additions & 104 deletions
This file was deleted.

.github/ISSUE_TEMPLATE/2-scanner_run_dfa_bug.yml

Lines changed: 0 additions & 117 deletions
This file was deleted.

0 commit comments

Comments
 (0)