zrzk
/
px4_autopilot
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
40844 Commits
14 Branches
0 Tags
306 MiB
Branch: pr-sensor-distance
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'pr-sensor-distance'
${ noResults }
px4_autopilot/.github/PULL_REQUEST_TEMPLATE.md

18 lines
804 B
Raw Permalink Normal View History Unescape

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.
6 years ago
Please use [PX4 Discuss](http://discuss.px4.io/) or [Slack](http://slack.px4.io/) to align on pull requests if necessary. You can then open draft pull requests to get early feedback.
Create PULL_REQUEST_TEMPLATE.md
7 years ago
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
3 years ago
## 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)
5 years ago
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.
6 years ago
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
3 years ago
## Describe your solution
Create PULL_REQUEST_TEMPLATE.md
7 years ago
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
3 years ago
## Describe possible alternatives
Create PULL_REQUEST_TEMPLATE.md
7 years ago
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
3 years ago
## Test data / coverage
PULL_REQUEST_TEMPLATE: change order of titles (#13174)
5 years ago
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
3 years ago
## 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.
6 years ago
Add any other related context or media.