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: docs/ide/developer-community-guidelines.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -29,21 +29,21 @@ If you can't find an existing issue that describes your bug or feature, submit a
29
29
30
30
1. File only one problem or feature request per issue.
31
31
32
-
- Combining multiple problems or feature requests into a single issue makes it harder for us to diagnose, and harder for other users to vote for your issue.
33
-
- Don't add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar but have different causes, which makes it harder for us to diagnose your issue.
32
+
- Combining multiple problems or feature requests into a single issue makes it harder for us to diagnose, and harder for other users to vote for your issue.
33
+
- Don't add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar but have different causes, which makes it harder for us to diagnose your issue.
34
34
35
35
2. The more information you can provide, the easier it will be for us to reproduce and fix your issue.
36
36
3. Include the following steps with each issue.
37
37
38
-
- Reproducible steps (1... 2... 3...) and what you expected versus what you experienced.
39
-
- Images, animations, or a link to a video. Images and animations illustrate repro-steps but _don't_ replace them.
40
-
- As appropriate, a code snippet that demonstrates the issue or a link to a code repository we can easily pull down onto our machine to recreate the issue.
38
+
- Reproducible steps (1... 2... 3...) and what you expected versus what you experienced.
39
+
- Images, animations, or a link to a video. Images and animations illustrate repro-steps but _don't_ replace them.
40
+
- As appropriate, a code snippet that demonstrates the issue or a link to a code repository we can easily pull down onto our machine to recreate the issue.
41
41
42
42
4. Remember to do the following steps:
43
43
44
-
- Search to see if there exists a duplicate. If so, vote up the existing issue, providing additional comments or clarifications as needed.
45
-
- Recreate the issue after disabling all extensions. If you find the issue is caused by an extension you've installed, file an issue on the extension respectively.
46
-
- Simplify your code around the issue so we can better isolate the problem.
44
+
- Search to see if there exists a duplicate. If so, vote up the existing issue, providing additional comments or clarifications as needed.
45
+
- Recreate the issue after disabling all extensions. If you find the issue is caused by an extension you've installed, file an issue on the extension respectively.
46
+
- Simplify your code around the issue so we can better isolate the problem.
47
47
48
48
Note that even with issues that include rich details, we may not be able to reproduce the issue and may ask for more information!
0 commit comments