contributing to Office 365 developer patterns and practices
Clone this wiki locally
Office 365 Developer Patterns and Practices (PnP) is a community project and we really appreciate it if you would contribute by creating new samples, fixing bugs in existing code, updating documentation. The typical way to do this in GitHub is by forking the Office 365 Developer Patterns and Practices repo, make your changes and then send them back via a pull request. The below links will help you setup your environment and will explain how you can create a pull request.
- Web cast: how to contribute to Office Dev PnP
- Setting up your environment for getting latest changes from GitHub using Visual Studio
- Preparing a contribution and letting the PnP core team know via pull request for contributing back (submissions are more than welcome)
Before we can accept your pull requests you will be asked to sign electronically Contributor License Agreement (CLA), which is prerequisite for any contributions to PnP repository. This will be one time process, so for any future contributions you will not be asked to re-sign anything. After the CLA has been signed, our PnP core team members will have a look on your submission for final verification of the submission. Please do not delete your development branch until the submission has been closed.
If you're a member of the Office 365 Developer Patterns and Practices core team one of the activities you do is merging pull requests that are created by the contributors. Below instructions describe how the above model (everyone works in their own forked repo) can be extended for core members.
Thanks for spending your time and energy to further enhance this project!
Contribution guidance for the code and articles
- Do not use emoticons in the code or articles
- Submit one PR for specific changes, avoid combining too many commits to one pull request
- Do not delete your feature branch before pull request has been processed by PnP core team