Clarification of time formats#10796
Closed
akasma74 wants to merge 20 commits into
Closed
Conversation
* Update changelog.markdown * Update changelog.markdown
* Add Airly documentation * Change ha_category * Update airly.markdown file * Update ha_release * Fix ha_release version Co-Authored-By: Klaas Schoute <klaas_schoute@hotmail.com> * Update ha_release version Co-Authored-By: Martin Hjelmare <marhje52@kth.se> * Fix typo Co-Authored-By: Martin Hjelmare <marhje52@kth.se> * ✏️ Tweaks
* inital commit * Update neato.markdown
* Move file to correct location * Add heading
* Add scene apply docs * Fix lint * Fix formatting
* Remove hipchat * Remove hipchat
* Add documentation about new key: time_format Based on PR home-assistant/home-asssitant#26940 this adds athe documentation about the new key + a warning on relying to much on the time based sensors. * Remove time_format key as it doesn't belong in backend * Remove time_format from the full configuration example * Add info about time being represented as UTC
script support added in home-assistant/core#27223
* add title option to stack cards * Update horizontal-stack.markdown * Update vertical-stack.markdown
I couldn't find anything in the current docs on time formats and thought it would be useful to give more details (rather than time | integer description) about ones available.
Member
|
Please rebase to the |
Converted them into paragraphs' headers instead, hope it's ok
Contributor
Author
|
Rebased and comverted extra tags into paragraphs' headers, please check it out. |
Member
|
Hi there @akasma74, I don't see a rebase, the only thing I see is that you've changed the target branch. Could you please rebase the PR's onto the Feel free to ask if you need any help with that. |
Contributor
Author
|
Hi @frenck , tbh I don't know how to rebase PRs so any help is highly appreciated. Update: I ended up creating a new PR to the current branch to speed up things. |
akasma74
added a commit
to akasma74/home-assistant.io
that referenced
this pull request
Oct 16, 2019
This PR superceeds home-assistant#10796 (couldn't rebase that). I couldn't find anything in the current docs on time formats and thought it would be useful to give more details (rather than time | integer description) about ones available.
2 tasks
Member
|
Thanks for creating a new PR, however, you didn't have to. I would have rebased it for you.... |
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.
I couldn't find anything in the current docs on time formats and thought it would be useful to give more details (rather than time | integer description) about ones available.
Description:
Pull request in home-assistant (if applicable): home-assistant/home-assistant#
Checklist:
nextis for changes and new documentation that will go public with the next Home Assistant release. Fixes, changes and adjustments for the current release should be created againstcurrent.