Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note about alternative weather integrations to Dark Sky #15147

Merged
merged 1 commit into from Oct 10, 2020

Conversation

SeanPM5
Copy link
Contributor

@SeanPM5 SeanPM5 commented Oct 10, 2020

Proposed change

I made this change on the Dark Sky sensors page, now adding the same message to the Weather entity version.

Since new users can't get an API key, and existing users have a year to switch, makes sense to point users to alternatives.

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:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue:

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.

I made this change on the Dark Sky **sensors** page, now adding the same message to the Weather entity version. 

Since new users can't get an API key, and existing users have a year to switch, makes sense to point users to alternatives.
@probot-home-assistant probot-home-assistant bot added current This PR goes into the current branch Hacktoberfest An PR on this issue (or the PR itself) is eligible towards Hacktoberfest! labels Oct 10, 2020
Copy link
Member

@fabaff fabaff left a comment

Choose a reason for hiding this comment

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

Thanks

@fabaff fabaff merged commit 44b1623 into current Oct 10, 2020
@delete-merged-branch delete-merged-branch bot deleted the SeanPM5-darksky branch October 10, 2020 10:12
@frenck frenck added this to Ready for review in Content improvements via automation Oct 10, 2020
@frenck frenck moved this from Ready for review to Done in Content improvements Oct 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
current This PR goes into the current branch Hacktoberfest An PR on this issue (or the PR itself) is eligible towards Hacktoberfest!
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants