Skip to content

Commit 75c2788

Browse files
authored
Update CONTRIBUTING.md
1 parent 530189e commit 75c2788

File tree

1 file changed

+17
-7
lines changed

1 file changed

+17
-7
lines changed

CONTRIBUTING.md

Lines changed: 17 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,18 +13,28 @@
1313

1414
### Reporting Bugs
1515

16-
This section guides you through submitting a bug report for Unity Library. Following these guidelines helps maintainers and the community understand your report :pencil:, reproduce the behavior :computer: :computer:, and find related reports :mag_right:.
16+
You can test the existing utitlties and report us the bugs/improvements/ideas.
1717

18-
Always add a meaningful title to your bug or issue.
18+
Always add a meaningful title to your issue.
1919

20-
> **Note**: If you find a **Closed** issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.
20+
### Adding Content to Wiki
2121

22-
If you have experienced any problems with the scripts and content that Unity Library provides, you can submit them to us at [Unity Library Issues Section](https://github.com/UnityCommunity/UnityLibrary/issues)
22+
You add tutorials and usage guideline for your content or existing content at [Wiki](https://github.com/UnityCommunity/UnityLibrary/wiki)
2323

24-
### Adding Content to Wiki
24+
Always add a good and meaningful title and content.
25+
26+
### Adding Content to Library
27+
28+
You can add your own content and utilities to the library by [making pull requests](https://github.com/UnityCommunity/UnityLibrary/pulls).
2529

26-
Also you can add content to [Unity Library Wiki](https://github.com/UnityCommunity/UnityLibrary/wiki) but always provide a full and complete content not a partial and error container.
30+
Always check the library to make sure you aren't adding a duplicate.
31+
32+
Always test your utitlity to make sure it works as expected and is error free.
33+
34+
Also you can make a new folder in the relevant category for your utility and include a README.md file for that to provide documentation and usage guideline.
2735

2836
### Making Pull Requests
2937

30-
You can submit your [Pull Requests](https://github.com/UnityCommunity/UnityLibrary/pulls) to us and we will merge them when they are ready. always add a meaningful pull request title.
38+
You can submit your [Pull Requests](https://github.com/UnityCommunity/UnityLibrary/pulls) to us and we will merge them when they are ready.
39+
40+
Always add a meaningful pull request title.

0 commit comments

Comments
 (0)