dark0707
/
px4-firmware
forked from Archive/PX4-Autopilot
1
0
Fork 0
Code Pull Requests Activity
px4-firmware/.github/PULL_REQUEST_TEMPLATE.md

18 lines
814 B
Markdown
Raw Normal View History

README.md update for discord
2022-10-27 02:01:37 -03:00
Please use [PX4 Discuss](http://discuss.px4.io/) or [Discord](https://discord.gg/dronecode) to align on pull requests if necessary. You can then open draft pull requests to get early feedback.
Create PULL_REQUEST_TEMPLATE.md
2018-07-08 18:19:24 -03:00
Update Issue and Pull Request Templates 1. Change the paragraph headings to proper Markdown headings (easier to link / structure the Markdown) 2. Move PULL_REQUEST_TEMPLATE into .github folder 3. Change description in Issue template and remove outdated DevGuide Repository information 4. Add a bug emoji to bug report isue template 5. Support automatically adding labels 'bug-report' and 'feature-request' to easily sort / filter appropriate issues in Github
2022-05-19 08:49:37 -03:00
## Describe problem solved by this pull request
A clear and concise description of the problem this proposed change will solve. Or, what it will improve.
PULL_REQUEST_TEMPLATE: change order of titles (#13174)
2019-10-14 08:11:44 -03:00
E.g. For this use case I ran into...
pull_request_template: order and phrasing Since I reorder the points every time I open a pull request I thought I might as well propose this order for the template.
2019-05-16 04:43:34 -03:00
Update Issue and Pull Request Templates 1. Change the paragraph headings to proper Markdown headings (easier to link / structure the Markdown) 2. Move PULL_REQUEST_TEMPLATE into .github folder 3. Change description in Issue template and remove outdated DevGuide Repository information 4. Add a bug emoji to bug report isue template 5. Support automatically adding labels 'bug-report' and 'feature-request' to easily sort / filter appropriate issues in Github
2022-05-19 08:49:37 -03:00
## Describe your solution
Create PULL_REQUEST_TEMPLATE.md
2018-07-08 18:19:24 -03:00
A clear and concise description of what you have implemented.
Update Issue and Pull Request Templates 1. Change the paragraph headings to proper Markdown headings (easier to link / structure the Markdown) 2. Move PULL_REQUEST_TEMPLATE into .github folder 3. Change description in Issue template and remove outdated DevGuide Repository information 4. Add a bug emoji to bug report isue template 5. Support automatically adding labels 'bug-report' and 'feature-request' to easily sort / filter appropriate issues in Github
2022-05-19 08:49:37 -03:00
## Describe possible alternatives
Create PULL_REQUEST_TEMPLATE.md
2018-07-08 18:19:24 -03:00
A clear and concise description of alternative solutions or features you've considered.
Update Issue and Pull Request Templates 1. Change the paragraph headings to proper Markdown headings (easier to link / structure the Markdown) 2. Move PULL_REQUEST_TEMPLATE into .github folder 3. Change description in Issue template and remove outdated DevGuide Repository information 4. Add a bug emoji to bug report isue template 5. Support automatically adding labels 'bug-report' and 'feature-request' to easily sort / filter appropriate issues in Github
2022-05-19 08:49:37 -03:00
## Test data / coverage
PULL_REQUEST_TEMPLATE: change order of titles (#13174)
2019-10-14 08:11:44 -03:00
How was it tested? What cases were covered? Logs uploaded to https://review.px4.io/ and screenshots of the important plot parts.
Update Issue and Pull Request Templates 1. Change the paragraph headings to proper Markdown headings (easier to link / structure the Markdown) 2. Move PULL_REQUEST_TEMPLATE into .github folder 3. Change description in Issue template and remove outdated DevGuide Repository information 4. Add a bug emoji to bug report isue template 5. Support automatically adding labels 'bug-report' and 'feature-request' to easily sort / filter appropriate issues in Github
2022-05-19 08:49:37 -03:00
## Additional context
pull_request_template: order and phrasing Since I reorder the points every time I open a pull request I thought I might as well propose this order for the template.
2019-05-16 04:43:34 -03:00
Add any other related context or media.