Skip to content

Commit eebb6ae

Browse files
authored
Update contributing.md
1 parent 85f50b1 commit eebb6ae

File tree

1 file changed

+13
-23
lines changed

1 file changed

+13
-23
lines changed

contributing.md

Lines changed: 13 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
Thank you for exhibiting interest in contributing to the Windows Community Toolkit. The team is delighted to welcome you onboard to our exciting and growing project. Any contribution or value added go a long way to enhance the project!
44

5-
In the next few steps you will be able to see a glimpse of ways you can contribute to the Windows Community Toolkit
5+
In the next few steps, you will be able to see a glimpse of ways you can contribute to the Windows Community Toolkit.
66

77
:rotating_light: **It is highly recommended to visit [Windows Community Toolkit Wiki](https://aka.ms/wct/wiki) where you can find complete and detail-oriented content of this page** :rotating_light:
88

@@ -11,39 +11,29 @@ Due to the high volume of incoming issues please keep our GitHub issues for bug
1111

1212
For missing documentation related question, please file an issue at [Microsoft Docs](https://github.com/MicrosoftDocs/WindowsCommunityToolkitDocs/issues/new).
1313

14-
## <a name="issue"></a> Fix a Bug :bug:
14+
## <a name="bug"></a> Fix a Bug :bug:
1515
If you find any bug, you can help the community by [submitting an issue](https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/new?assignees=&labels=bug+%3Abug%3A&template=bug_report.md&title=). Once the issue is filed, feel free to start working on the PR and submit a PR.
1616

17-
## <a name="first-issue"></a>Good First Issue :ok_hand:
17+
## <a name="issue"></a>Good First Issue :ok_hand:
1818
If this is your first time contributing to the Windows Community Toolkit and do not have advanced level programming experience, we have got you covered :boom: WCT has a list of [good first issue](https://github.com/windows-toolkit/WindowsCommunityToolkit/labels/good%20first%20issue%20%3Aok_hand%3A) that can be a great entryway to find and fix any issues that best fit your expertise or technical background.
1919

20-
## <a name="help-wanted"></a>Help Wanted :raising_hand:
21-
WCT has a list of issues that are labeled as [help wanted](https://github.com/windows-toolkit/WindowsCommunityToolkit/labels/help%20wanted%20%3Araising_hand%3A). The level of complexity in this list of issues can vary but if you have an advanced level of programming experience you can also jump in to solve these issues.
20+
## <a name="help"></a>Help Wanted :raising_hand:
21+
WCT has a list of issues that are labeled as [help wanted](https://github.com/windows-toolkit/WindowsCommunityToolkit/labels/help%20wanted%20%3Araising_hand%3A). The level of complexity in the list can vary but if you have an advanced level of programming experience, feel free to jump in to solve these issues.
2222

23-
## <a name="create-pr"></a>Create Pull Request :rocket:
24-
Anyone with write access can create a Pull Request by forking the Windows Community Toolkit Repository. Here is how you can [Create a Pull Request from fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork).
25-
26-
Once you fork the Windows Community Toolkit repo, it is essential to create all changes in the feature branch of your forked repository. If you have the changes in the forked feature branch you can create a Pull Request in the main Windows Community Toolkit where your changes will be reviewed to be merged to the Master.
27-
28-
:warning: **We will not merge the PR to the main repo if your changes are not in the feature branch of your forked repository** :warning:
29-
30-
31-
## <a name="submit-pr"></a>Submit or Review Pull Request :rocket:
32-
33-
Please visit [Windows Community Toolkit Wiki](https://aka.ms/wct/wiki) for detailed information and steps it require to Submit or Review Pull Request.
34-
35-
36-
## <a name="pr"></a>Add New Feature :mailbox_with_mail:
23+
## <a name="feature"></a>Add New Feature :mailbox_with_mail:
3724
* To contribute a new feature, fill out the [Feature Request Template](https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/new?assignees=&labels=feature+request+%3Amailbox_with_mail%3A&template=feature_request.md&title=%5BFeature%5D) and provide detailed information to express the proposal.
3825
* Once the Feature Request is submitted, it will be open for discussion.
3926
* If it gets approved by the team, proceed to submit a PR of the proposed Feature.
4027
* If the PR contains an error-free code and the reviewer signs off, the PR will be merged.
4128

4229
## <a name="docs"></a> Add or Improve Documentation :page_with_curl:
4330

44-
Due to the multiple steps invovled to add or improve documents; it is required to visit [Windows Community Toolkit Wiki](https://aka.ms/wct/wiki) to follow contribution guidelines.
31+
Due to the involvement of multiple steps to add or improve documents; it is required to visit [Windows Community Toolkit Wiki](https://aka.ms/wct/wiki) and follow contribution guidelines.
32+
33+
## <a name="pr"></a>Create, Submit or Review Pull Request :rocket:
34+
Anyone with write access can create a Pull Request by forking the Windows Community Toolkit Repository. Here is how you can [Create a Pull Request from fork](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork). Once you fork the Windows Community Toolkit repo, it is essential to create all changes in the feature branch of your forked repository. If you have the changes in the forked feature branch, you can then create a Pull Request in the main Windows Community Toolkit.
4535

46-
36+
Please visit [Windows Community Toolkit Wiki](https://aka.ms/wct/wiki) for detailed information and steps it requires to Submit or Review Pull Request.
4737

48-
# Thank You :heart::heart:
49-
**Thank you so much for participating and contributing in this amazing project. We hope you continue to find yourself a strong asset to the Windows Community Toolkit and always find this platform highly reliable.**
38+
# ThankYou :heart::heart:
39+
**Thank you so much for contributing to this amazing project. We hope you will continue to add value and find yourself as a highly reliable source to the Windows Community Toolkit**

0 commit comments

Comments
 (0)