-
Notifications
You must be signed in to change notification settings - Fork 3
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
[FR] HACS support #5
Comments
I think this is a great idea. I will be happy to look at this. |
I think we need an icon too. Any ideas? |
Go ahead Will, I am very busy this weeks, but feel free to do anything you want! Will be following up via emails, so feel free to ping me anywhere. Thanks again for all the work! |
Icon added. I took a free bulb icon and added a colour wheel in Inkscape. Let me know what you think. |
looks great! |
PR for brands icon: home-assistant/brands#4939 |
@raulgbcr when you get a moment, can you add some "topics" to the repo as per: https://hacs.xyz/docs/publish/start#topics |
done! |
Add hessfest action as part of HACS. Helps #5
Created hassfest action as per: https://developers.home-assistant.io/blog/2020/04/16/hassfest/ |
Sort keys by alphabetical order expect for domain and name which must be at the top. Required to pass hassfest linting. Helps #5
@raulgbcr In order to have our PR accepted in to HACS we have to cut a new release after the Hacsfest validation checks started passing. As such, can you cut a new minor release? Once the new release is done I have a PR for HACS, and we are done!! |
Thats awesome!!! Thank you again for everything!!
Done! I believe you should be able to do it too, I just create a tag and upload the file with the |
PR: For inclusion in HACS proper: hacs/default#2208 |
cool! There was a little error with the release zip, zipped the wrong folder, have fixed it now |
I think we might be waiting a long time for the PR in HACS to merge. There is a backlog of hundreds going back to September. So I'm going to close this issue as the work on our end is, as far as I can tell, completed. We're in a good state following this work:
|
Whoops! I deleted the forked HACS repo with the main inclusion request before it was merged. I've created another one: hacs/default#2345 |
It would be awesome if you added support for HACS - even as a custom repo.
The only thing that seems to be needed is adding the
hacs.json
file to the root of the repo, with the following basic content:Then the users can add the repo directly to HACS and let it manage versions whenever a release is made.
The text was updated successfully, but these errors were encountered: