| 1 |
# Contributing to Embed Privacy |
| 2 |
|
| 3 |
First, we’re happy to have you here! Thank you for taking time to contribute. :tada: :heart: |
| 4 |
|
| 5 |
## Language |
| 6 |
|
| 7 |
Even if we are based in Germany and thus speak German as well, please use English primarily in discussions on the Embed Privacy GitHub project. Use German only if you struggle to find the correct words in English. |
| 8 |
|
| 9 |
## Creating issues |
| 10 |
|
| 11 |
Before creating a new issue, please search for existing issues targeting the same problem. |
| 12 |
|
| 13 |
Please use the available issue templates for bugs and feature requests and give as much information as possible. |
| 14 |
|
| 15 |
## Adding code |
| 16 |
|
| 17 |
If you want to contribute code, please create an issue first so that we can discuss if the functionality you want to implement is intended to be a reasonable value for Embed Privacy. |
| 18 |
|
| 19 |
### Code style |
| 20 |
|
| 21 |
We’re using the [](https://github.com/epiphyt/EpiphytCodingStandardEpiphytCodingStandard](https://github.com/epiphyt/EpiphytCodingStandard](https://github.com/epiphyt/EpiphytCodingStandard), which is a more strict adaptation of the WordPress Coding Standard for PHP Code. This coding standard is mandatory for every code change. |
| 22 |
|
| 23 |
### Testing |
| 24 |
|
| 25 |
Please make sure that your code is tested in a clean environment. A huge plus will be to know the code is tested in both a single and a multisite installation. |
| 26 |
|
| 27 |
### Commit message |
| 28 |
|
| 29 |
We use [](https://gitmoji.devgitmoji](https://gitmoji.dev](https://gitmoji.dev) to get a decent overview over what’s the purpose of a single commit. Thus, you should use them as well. |
| 30 |
|
