Skip to content

Commit a17dcb5

Browse files
author
Ramya
committed
Adding CONTRIBUTING.md file
1 parent 29f2291 commit a17dcb5

File tree

1 file changed

+81
-0
lines changed

1 file changed

+81
-0
lines changed

CONTRIBUTING.md

+81
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
# Contributing to Azure samples
2+
3+
Thank you for your interest in contributing to Azure samples!
4+
5+
# Contributing to [project-title]
6+
7+
This project welcomes contributions and suggestions. Most contributions require you to agree to a
8+
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
9+
the rights to use your contribution. For details, visit https://cla.microsoft.com.
10+
11+
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
12+
a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
13+
provided by the bot. You will only need to do this once across all repos using our CLA.
14+
15+
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
16+
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
17+
contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
18+
19+
- [Code of Conduct](#coc)
20+
- [Issues and Bugs](#issue)
21+
- [Feature Requests](#feature)
22+
- [Submission Guidelines](#submit)
23+
24+
## <a name="coc"></a> Code of Conduct
25+
Help us keep this project open and inclusive. Please read and follow our [Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
26+
27+
## <a name="issue"></a> Found an Issue?
28+
If you find a bug in the source code or a mistake in the documentation, you can help us by
29+
[submitting an issue](#submit-issue) to the GitHub Repository. Even better, you can
30+
[submit a Pull Request](#submit-pr) with a fix.
31+
32+
## <a name="feature"></a> Want a Feature?
33+
You can *request* a new feature by [submitting an issue](#submit-issue) to the GitHub
34+
Repository. If you would like to *implement* a new feature, please submit an issue with
35+
a proposal for your work first, to be sure that we can use it.
36+
37+
* **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
38+
39+
## <a name="submit"></a> Submission Guidelines
40+
41+
### <a name="submit-issue"></a> Submitting an Issue
42+
Before you submit an issue, search the archive, maybe your question was already answered.
43+
44+
If your issue appears to be a bug, and hasn't been reported, open a new issue.
45+
Help us to maximize the effort we can spend fixing issues and adding new
46+
features, by not reporting duplicate issues. Providing the following information will increase the
47+
chances of your issue being dealt with quickly:
48+
49+
* **Overview of the Issue** - if an error is being thrown a non-minified stack trace helps
50+
* **Version** - what version is affected (e.g. 0.1.2)
51+
* **Motivation for or Use Case** - explain what are you trying to do and why the current behavior is a bug for you
52+
* **Browsers and Operating System** - is this a problem with all browsers?
53+
* **Reproduce the Error** - provide a live example or a unambiguous set of steps
54+
* **Related Issues** - has a similar issue been reported before?
55+
* **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be
56+
causing the problem (line of code or commit)
57+
58+
You can file new issues by providing the above information at the corresponding repository's issues link: https://github.com/[organization-name]/[repository-name]/issues/new].
59+
60+
### <a name="submit-pr"></a> Submitting a Pull Request (PR)
61+
Before you submit your Pull Request (PR) consider the following guidelines:
62+
63+
* Search the repository (https://github.com/[organization-name]/[repository-name]/pulls) for an open or closed PR
64+
that relates to your submission. You don't want to duplicate effort.
65+
66+
* Make your changes in a new git fork:
67+
68+
* Commit your changes using a descriptive commit message
69+
* Push your fork to GitHub:
70+
* In GitHub, create a pull request
71+
* If we suggest changes then:
72+
* Make the required updates.
73+
* Rebase your fork and force push to your GitHub repository (this will update your Pull Request):
74+
75+
```shell
76+
git rebase master -i
77+
git push -f
78+
```
79+
80+
That's it! Thank you for your contribution!
81+

0 commit comments

Comments
 (0)