|
1 |
| -# 🎉 Thanks for taking the time to contribute to Analytics.js! 🎉 |
| 1 | +## Description |
2 | 2 |
|
3 |
| -It is highly appreciated that you take the time to help improve Analytics.js. |
4 |
| -We appreciate it if you would take the time to document your Pull Request. |
| 3 | +<!-- # 🎉 Thanks for contributing to Analytics.js! We really appreciate your time. 🎉 |
5 | 4 |
|
6 |
| -Sadly, if we don't receive enough information, or the Pull Request doesn't |
7 |
| -align well with our roadmap, we might respectfully thank you for your time, and close the issue. |
| 5 | +To help us quickly assess your work, please document your Pull Request using this template. |
| 6 | +
|
| 7 | +Sadly, we can't merge all PRs - but you can multiply the chances of your change getting in by giving us the information we need. If the Pull Request doesn't align well with our roadmap, we might respectfully thank you for your time, and close the issue. --> |
| 8 | + |
| 9 | +## Test plan |
| 10 | + |
| 11 | +<!-- Provide all possible documentation: screenshots, sh commands, etc. |
| 12 | +For change control purposes, use the following pattern: |
| 13 | +
|
| 14 | +- Testing completed successfully using <how did you test, environment>; or |
| 15 | +- Testing not required because <explain why you think testing isn't needed> |
| 16 | +--> |
| 17 | + |
| 18 | +## Release plan |
| 19 | + |
| 20 | +<!-- Update the HISTORY.md file if we need to generate a new version of AJS for your changes. |
| 21 | +
|
| 22 | +If not, just add the following line with an explanation: |
| 23 | +Release not necessary because <verbose explantaion - for example 'it's a dev-only change'>. |
| 24 | +--> |
8 | 25 |
|
9 | 26 | ## Checklist
|
10 | 27 |
|
11 |
| -Please ensure the following are completed to help get your PR merged: |
| 28 | +<!-- |
| 29 | +Make sure you complete the following checklist to help get your PR merged:--> |
| 30 | + |
12 | 31 |
|
13 | 32 | - [ ] Thorough explanation of the issue/solution, and a link to the related issue
|
14 | 33 | - [ ] CI tests are passing
|
15 | 34 | - [ ] Unit tests were written for any new code
|
16 | 35 | - [ ] Code coverage is at least maintained, or increased.
|
17 | 36 |
|
| 37 | +<!-- |
18 | 38 | ## Respect earns Respect 👏
|
19 | 39 |
|
20 | 40 | Please respect our Code of Conduct, in short:
|
21 | 41 |
|
22 |
| -- Using welcoming and inclusive language. |
23 |
| -- Being respectful of differing viewpoints and experiences. |
24 |
| -- Gracefully accepting constructive criticism. |
25 |
| -- Focusing on what is best for the community. |
26 |
| -- Showing empathy towards other community members. |
| 42 | +- Use welcoming and inclusive language. |
| 43 | +- Be respectful of differing viewpoints and experiences. |
| 44 | +- Gracefully accept constructive criticism. |
| 45 | +- Focus on what is best for the community. |
| 46 | +- Show empathy toward other community members. |
| 47 | +
|
| 48 | +--> |
0 commit comments