@@ -25,9 +25,9 @@ Note: If you wish to work on something that already exists on our backlog, you
1. Fork the repository. Click on the "Fork" button on the top right of the page and follow the flow.
2. If your work needs more time, the consider branching off of master else just code in your fork.
3. Ensure your changes check for the appropriate device families (ex: Windows Desktop and IoT only).
4. Implement one or more [tests](https://github.com/Microsoft/WindowsDevicePortalWrapper/blob/master/Testing.md) to ensure the change works on the target platform(s).
5. Make small and frequent commits that include [tests](https://github.com/Microsoft/WindowsDevicePortalWrapper/blob/master/Testing.md) against mock data or manual tests which can be run against real devices.
6. Make sure that all existing [tests](https://github.com/Microsoft/WindowsDevicePortalWrapper/blob/master/Testing.md) continue to pass.
4. Implement one or more [tests](Testing.md) to ensure the change works on the target platform(s).
5. Make small and frequent commits that include [tests](Testing.md) against mock data or manual tests which can be run against real devices.
6. Make sure that all existing [tests](Testing.md) continue to pass.
@@ -3,12 +3,12 @@ A client library that wraps the [Windows Device Portal](https://msdn.microsoft.c
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
[Get Started](https://github.com/Microsoft/WindowsDevicePortalWrapper/blob/master/GettingStarted.md) using the library.
[Get Started](GettingStarted.md) using the library.
---
---
To start contributing, see [Contributing](https://github.com/Microsoft/WindowsDevicePortalWrapper/blob/master/CONTRIBUTING.md).
To start contributing, see [Contributing](CONTRIBUTING.md).
```
Note: The contribution guidelines were updated in January 2018. Pull requests that target the master branch will be asked to be retargeted to the Development branch prior to approval.
