You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/BUG_REPORT.yml
+1-13Lines changed: 1 addition & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -20,18 +20,6 @@ body:
20
20
label: Editor
21
21
description: Which text editor are you using (and LSP extension/plugin if applicable)?
22
22
placeholder: Eg. Visual Studio Code with Swift extension 1.9.0, Neovim
23
-
- type: dropdown
24
-
id: reproduces-with-swift-6
25
-
attributes:
26
-
label: Does the issue reproduce with Swift 6?
27
-
description: |
28
-
Does the issue also reproduce using a [recent Swift 6 Development Snapshot](https://www.swift.org/download/#swift-60-development)?
29
-
30
-
We have made significant changes to SourceKit-LSP in Swift 6 and the issue might have already been fixed. If you didn’t try, that is fine.
31
-
options:
32
-
- "Yes"
33
-
- "No"
34
-
- I didn’t try
35
23
- type: textarea
36
24
id: description
37
25
attributes:
@@ -49,5 +37,5 @@ body:
49
37
attributes:
50
38
label: Logging
51
39
description: |
52
-
If you are using SourceKit-LSP from Swift 6, running `sourcekit-lsp diagnose` in terminal and attaching the generated bundle helps us diagnose the issue.
40
+
Run `sourcekit-lsp diagnose` in terminal and attach the generated bundle to help us diagnose the issue.
53
41
The generated bundle may contain paths to files on disk as well as portions of your source code. This greatly helps in reproducing issues, but you should only attach it if you feel comfortable doing so.
0 commit comments