Update hass.markdown#5193
Merged
Merged
Conversation
Member
|
|
3 tasks
Contributor
Author
|
Hey @fabaff, I'm in the process of creating the pull request in the other branch now. Both of the PR templates contain "reference to PR in other branch containing your doc changes". It was a chicken and egg problem so I made this PR first and was going to update it with a number as soon as I got the other one published. See home-assistant/core#13929 for the PR in question. |
Member
|
Sorry, my bad. |
Contributor
Author
|
No worries. Honestly, I'd rather you be as on top of things as you are then never responding at all. |
frenck
approved these changes
Apr 19, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Add documentation for --log-no-color command line switch
Pull request in home-assistant (if applicable): home-assistant/core#13929
Checklist:
current. New documentation for platforms/components and features should go tonext.