Skip to content

Update VeSync documentation to reflect library updates#22919

Merged
MartinHjelmare merged 1 commit intohome-assistant:nextfrom
jetpacktuxedo:vesync-docs
May 30, 2022
Merged

Update VeSync documentation to reflect library updates#22919
MartinHjelmare merged 1 commit intohome-assistant:nextfrom
jetpacktuxedo:vesync-docs

Conversation

@jetpacktuxedo
Copy link
Copy Markdown
Contributor

Proposed change

Update documentation to reflect changes from core pr 72658.

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

  • Link to parent pull request in the codebase: Vesync air quality core#72658
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue: fixes #

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

@probot-home-assistant probot-home-assistant Bot added has-parent This PR has a parent PR in another repo in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch labels May 30, 2022
@probot-home-assistant probot-home-assistant Bot added the current This PR goes into the current branch label May 30, 2022
@probot-home-assistant
Copy link
Copy Markdown

It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the next branch. Please change the target branch of this PR to next and rebase if needed.
(message by DocsTargetBranch)

@jetpacktuxedo jetpacktuxedo changed the base branch from current to next May 30, 2022 16:31
Copy link
Copy Markdown
Member

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@probot-home-assistant probot-home-assistant Bot removed needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch in-progress This PR/Issue is currently being worked on parent-merged The parent PR has been merged already labels May 30, 2022
@MartinHjelmare MartinHjelmare added next This PR goes into the next branch parent-merged The parent PR has been merged already and removed current This PR goes into the current branch labels May 30, 2022
@MartinHjelmare MartinHjelmare merged commit 763893b into home-assistant:next May 30, 2022
@probot-home-assistant probot-home-assistant Bot removed the parent-merged The parent PR has been merged already label May 30, 2022
@github-actions github-actions Bot locked and limited conversation to collaborators May 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla-signed has-parent This PR has a parent PR in another repo next This PR goes into the next branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants