core/.github/PULL_REQUEST_TEMPLATE.md

## Breaking Change:

<!-- What is breaking and why we have to break it. Remove this section only if it was NOT a breaking change. -->

## Description:


**Related issue (if applicable):** fixes #<home-assistant issue number goes here>

**Pull request with documentation for [home-assistant.io](https://github.com/home-assistant/home-assistant.io) (if applicable):** home-assistant/home-assistant.io#<home-assistant.io PR number goes here>

## Example entry for `configuration.yaml` (if applicable):
```yaml

```

## Checklist:
  - [ ] The code change is tested and works locally.
  - [ ] Local tests pass with `tox`. **Your PR cannot be merged unless tests pass**
  - [ ] There is no commented out code in this PR.
  - [ ] I have followed the [development checklist][dev-checklist]

If user exposed functionality or configuration variables are added/changed:
  - [ ] Documentation added/updated in [home-assistant.io](https://github.com/home-assistant/home-assistant.io)

If the code communicates with devices, web services, or third-party tools:
  - [ ] [_The manifest file_][manifest-docs] has all fields filled out correctly. Update and include derived files by running `python3 -m script.hassfest`.
  - [ ] New or updated dependencies have been added to `requirements_all.txt` by running `python3 -m script.gen_requirements_all`.
  - [ ] Untested files have been added to `.coveragerc`.

If the code does not interact with devices:
  - [ ] Tests have been added to verify that the new code works.

[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
Add breaking change section to PR template (#21994) 2019-03-13 09:54:30 +00:00			`## Breaking Change:`

			`<!-- What is breaking and why we have to break it. Remove this section only if it was NOT a breaking change. -->`

Use H2 headers to split up the different sections (#6183) Using headers makes it easier to visually differentiate between the different sections 2017-02-23 20:58:18 +00:00			`## Description:`
Add initial templates 2016-02-26 21:38:15 +00:00

Update link to docs repo (#3886) 2016-10-15 11:46:45 +00:00			`Related issue (if applicable): fixes #<home-assistant issue number goes here>`
Update PULL_REQUEST_TEMPLATE.md 2016-02-28 08:59:28 +00:00
Update PR template (#23520) * Update PR template * Update config, PR template 2019-05-07 21:18:40 +00:00			`Pull request with documentation for [home-assistant.io](https://github.com/home-assistant/home-assistant.io) (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>`
Add lines for associated documentation PR 2016-05-14 21:02:14 +00:00
Use H2 headers to split up the different sections (#6183) Using headers makes it easier to visually differentiate between the different sections 2017-02-23 20:58:18 +00:00			## Example entry for `configuration.yaml` (if applicable):
Update with comments from PR 2016-02-27 22:17:20 +00:00			```yaml
Add initial templates 2016-02-26 21:38:15 +00:00
Update with comments from PR 2016-02-27 22:17:20 +00:00			```
Add initial templates 2016-02-26 21:38:15 +00:00
Use H2 headers to split up the different sections (#6183) Using headers makes it easier to visually differentiate between the different sections 2017-02-23 20:58:18 +00:00			`## Checklist:`
Update PULL_REQUEST_TEMPLATE.md (#11465) * Update PULL_REQUEST_TEMPLATE.md * Add period 2018-01-05 17:31:41 +00:00			`- [ ] The code change is tested and works locally.`
New lazytox.py script (#12862) 2018-03-09 20:27:39 +00:00			- [ ] Local tests pass with `tox`. Your PR cannot be merged unless tests pass
Update PR checklist with commented out code check (#18272) Along with hopefully helping resolve these actual problems, a nudge for people to look at their own code might help catch other quick fixes before anyone else has to review a PR. 2018-11-06 18:47:19 +00:00			`- [ ] There is no commented out code in this PR.`
Update PR template (#23520) * Update PR template * Update config, PR template 2019-05-07 21:18:40 +00:00			`- [ ] I have followed the [development checklist][dev-checklist]`
Add initial templates 2016-02-26 21:38:15 +00:00
Add lines for associated documentation PR 2016-05-14 21:02:14 +00:00			`If user exposed functionality or configuration variables are added/changed:`
Updates documentation repo URL in PR template (#16537) 2018-09-10 12:28:21 +00:00			`- [ ] Documentation added/updated in [home-assistant.io](https://github.com/home-assistant/home-assistant.io)`
Add lines for associated documentation PR 2016-05-14 21:02:14 +00:00
Fix sentence (#3709) 2016-10-05 14:28:38 +00:00			`If the code communicates with devices, web services, or third-party tools:`
Update PR template (#23520) * Update PR template * Update config, PR template 2019-05-07 21:18:40 +00:00			- [ ] [_The manifest file_][manifest-docs] has all fields filled out correctly. Update and include derived files by running `python3 -m script.hassfest`.
			- [ ] New or updated dependencies have been added to `requirements_all.txt` by running `python3 -m script.gen_requirements_all`.
			- [ ] Untested files have been added to `.coveragerc`.
Update PULL_REQUEST_TEMPLATE.md 2016-03-22 15:39:24 +00:00
			`If the code does not interact with devices:`
Update PULL_REQUEST_TEMPLATE.md 2016-02-28 08:59:28 +00:00			`- [ ] Tests have been added to verify that the new code works.`
Add initial templates 2016-02-26 21:38:15 +00:00
Update PR template (#23520) * Update PR template * Update config, PR template 2019-05-07 21:18:40 +00:00			`[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html`
			`[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html`