| 1 | Thank you for creating a pull request to contribute to Adafruit's GitHub code! |
| 2 | Before you open the request please review the following guidelines and tips to |
| 3 | help it be more easily integrated: |
| 4 | |
| 5 | - **Describe the scope of your change--i.e. what the change does and what parts |
| 6 | of the code were modified.** This will help us understand any risks of integrating |
| 7 | the code. |
| 8 | |
| 9 | - **Describe any known limitations with your change.** For example if the change |
| 10 | doesn't apply to a supported platform of the library please mention it. |
| 11 | |
| 12 | - **Please run any tests or examples that can exercise your modified code.** We |
| 13 | strive to not break users of the code and running tests/examples helps with this |
| 14 | process. |
| 15 | |
| 16 | Thank you again for contributing! We will try to test and integrate the change |
| 17 | as soon as we can, but be aware we have many GitHub repositories to manage and |
| 18 | can't immediately respond to every request. There is no need to bump or check in |
| 19 | on a pull request (it will clutter the discussion of the request). |
| 20 | |
| 21 | Also don't be worried if the request is closed or not integrated--sometimes the |
| 22 | priorities of Adafruit's GitHub code (education, ease of use) might not match the |
| 23 | priorities of the pull request. Don't fret, the open source community thrives on |
| 24 | forks and GitHub makes it easy to keep your changes in a forked repo. |
| 25 | |
| 26 | After reviewing the guidelines above you can delete this text from the pull request. |