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
+8-8
Original file line number
Diff line number
Diff line change
@@ -13,16 +13,16 @@ This project adheres to the [Open Code of Conduct][code-of-conduct]. By particip
13
13
14
14
## Submitting a pull request
15
15
16
-
0.[Fork][] and clone the repository (see Build Instructions in the [README][readme])
17
-
0. Create a new branch: `git checkout -b my-branch-name`
18
-
0. Make your change, add tests, and make sure the tests still pass
19
-
0. Push to your fork and [submit a pull request][pr]
20
-
0. Pat your self on the back and wait for your pull request to be reviewed and merged.
16
+
1.[Fork][] and clone the repository (see Build Instructions in the [README][readme])
17
+
2. Create a new branch: `git checkout -b my-branch-name`
18
+
3. Make your change, add tests, and make sure the tests still pass
19
+
4. Push to your fork and [submit a pull request][pr]
20
+
5. Pat your self on the back and wait for your pull request to be reviewed and merged.
21
21
22
22
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
23
23
24
-
- Follow the existing code's style.
25
-
- Write tests.
24
+
- Follow the style/format of the existing code.
25
+
- Write tests for your changes.
26
26
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
27
27
- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
28
28
@@ -38,7 +38,7 @@ There are certain areas of the extension that are restricted in what they can do
38
38
### Bug Reporting
39
39
40
40
Here are a few helpful tips when reporting a bug:
41
-
- Verify the bug resides in the GitHub for Visual Studio extension
41
+
- Verify that the bug resides in the GitHub for Visual Studio extension
42
42
- 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.
43
43
- 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
44
44
- Screenshots are very helpful in diagnosing bugs and understanding the state of the extension when it's experiencing problems. Please include them whenever possible.
0 commit comments