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
{{ message }}
This repository was archived by the owner on Jun 21, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+13-10Lines changed: 13 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,17 +37,20 @@ There are certain areas of the extension that are restricted in what they can do
37
37
38
38
Here are a few helpful tips when reporting a bug:
39
39
- Verify the bug resides in the GitHub for Visual Studio extension
40
-
- A lot of functionality within this extension resides in the Team Explorer pane, where there are additional tools to manage and collaborate on source code, including Visual Studio's Git Extension, which is owned by Microsoft.
40
+
- A lot of functionality provided by this extension resides in the Team Explorer pane, alongside other non-GitHub tools to manage and collaborate on source code, including Visual Studio's Git support, which is owned by Microsoft.
41
41
- If this bug not is related to the GitHub extension, visit the [Visual Studio support page](https://www.visualstudio.com/support/support-overview-vs) for help
42
-
- A log file can be helpful in diagnosing bug issues, if you'd like to include one in your issue, here is how you'd do it:
43
-
0. Close Visual Studio if it's open
44
-
0. Open a Developer Command Prompt for VS2015
45
-
0. Run devenv /log
46
-
0. Close VS
47
-
0. Locate the following files on your system and email them to [email protected] or copy their contents into the issue:
- Screenshots are also helpful in diagnosing bugs and understanding the state of the extension when it's experiencing problems.
42
+
- Screenshots are very helpful in diagnosing bugs and understanding the state of the extension when it's experiencing problems. Please include them whenever possible.
43
+
- A log file is helpful in diagnosing bug issues. To include log files in your issue:
44
+
45
+
1. Close Visual Studio if it's open
46
+
2. Open a Developer Command Prompt for VS2015
47
+
3. Run devenv /log
48
+
4. Reproduce your issue
49
+
5. Close VS
50
+
6. Locate the following files on your system and email them to [email protected] or create a gist and link it in the issue report:
If you have a feature that you think would be a great addition to the extension, we might already have thought about it too, so be sure to check if your suggestion matches our [roadmap](#roadmap-and-future-feature-ideas) before making a request. Also take a peek at our [pull requests](https://github.com/github/VisualStudio/pulls) to see what we're currently working on. Additionally, someone might have already thought of your idea, so check out Issues labeled as [features](https://github.com/github/VisualStudio/issues?q=is%3Aopen+is%3Aissue+label%3Afeature) to see if it already exists.
0 commit comments