Skip to content

Commit b47b7a0

Browse files
hillaryfraleyfabaff
authored andcommitted
Fixed typos and made organization suggestions (home-assistant#1116)
1 parent 320941b commit b47b7a0

File tree

1 file changed

+20
-9
lines changed

1 file changed

+20
-9
lines changed

source/developers/development_submitting.markdown

Lines changed: 20 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -9,18 +9,29 @@ sharing: true
99
footer: true
1010
---
1111

12-
Improvements, fixes, and new features to Home Assistant should be submitted one feature at a time using GitHub [Pull Requests](https://help.github.com/articles/using-pull-requests).
12+
Submit your improvements, fixes, and new features to Home Assistant one at a time, using GitHub [Pull Requests](https://help.github.com/articles/using-pull-requests). Here are the steps:
1313

14-
1. From your fork, create a new branch to hold your changes
14+
1. From your fork, create a new branch to hold your changes:
15+
1516
`git checkout -b some-feature`
16-
2. Make the changes you want, create a [new platform](/developers/add_new_platform/), develop a [new component](/developers/creating_components/), or fix [issues](https://github.com/home-assistant/home-assistant/issues).
17-
3. [Test your changes](/developers/development_testing/) and check for style violations
18-
4. Commit the changes if all [musts](/developers/development_checklist/) are covered.
17+
18+
2. Make your changes, create a [new platform](/developers/add_new_platform/), develop a [new component](/developers/creating_components/), or fix [issues](https://github.com/home-assistant/home-assistant/issues).
19+
20+
3. [Test your changes](/developers/development_testing/) and check for style violations.
21+
22+
4. If everything looks good according to these [musts](/developers/development_checklist/), commit your changes:
23+
1924
`git add .`
25+
2026
`git commit -m "Added some-feature"`
21-
5. Consider to add tests to ensure that the code works.
22-
6. Push your committed changes back to your fork on GitHub
27+
28+
* Consider adding tests to ensure that your code works.
29+
30+
5. Push your committed changes back to your fork on GitHub:
31+
2332
`git push origin HEAD`
24-
7. Follow [these steps](https://help.github.com/articles/creating-a-pull-request/) to create your pull request.
25-
8. Check for comments and suggestions on your Pull Request and keep an eye on the [CI output](https://travis-ci.org/home-assistant/home-assistant/).
33+
34+
6. Follow [these steps](https://help.github.com/articles/creating-a-pull-request/) to create your pull request.
35+
36+
7. Check for comments and suggestions on your pull request and keep an eye on the [CI output](https://travis-ci.org/home-assistant/home-assistant/).
2637

0 commit comments

Comments
 (0)