-
Notifications
You must be signed in to change notification settings - Fork 3
Enable GitHub workflows #11
Comments
@CyrielRct Could you add topics to the Repo? |
Sure it's done. I've done the same as the initial project. |
@attilaersek I'm not sure how to proceed could you help me with that ? |
@CyrielRct : Yup, i have an idea what could be the problem! I will open a PR quickly. |
@CyrielRct: though some workflows are a bit outdated, the hacs one was not. Checked the code what this check actually looks for. I recommend you to go to the editor, adjust the tags/topics to your taste and retry the action. |
Let me know if it was not enough. I can ignore this check in code until we figure it out. |
maybe I found it later, just follow from original georgezhao2010/midea_ac_lan repo issue and PR info and found it now. if we planed to continue work with it, maybe I can help to maintain it. and I will try to maintain it with us in future. |
Hello @CyrielRct what't the current status and future plan about this? Thanks |
Hi @wuwentao If you can take on this role I'll continue to help as much as I can but it's totally fine with me and I thank you. at this time here are people added to Collaborator status : @Qianli-Ma @attilaersek @rokam This project is clearly used by many person and need someone who's going to keep it going |
I see you already done it here : https://github.com/wuwentao/midea_ac_lan |
@CyrielRct I have forked it and just debug/config/testing/understanding with it. for release job with error input file name,I have add new github action, it will automatic zip release dir and upload to github release page , all the jobs will be finished by github actions, not our manual action. I'm also woking with HACS official repo to remove old one and add new fork with it, but it may cost more time, I'm not sure with the process time, once it down, I'll send update. I will add Collaborator, thank you for your detail info. |
@wuwentao @CyrielRct which repo fork should we try to start using? :) AFAISaw @wuwentao has already initiated the process of removing the unmaintained repo from HACS and add his fork to HACS. Should we use that repo? Ps: really open if I can be of any help. I'm a dev with GH experience :) |
@daniel-toth-leeder lets use @wuwentao fork |
please use my fork to do the future changes, and I will continue maintain it now. Thanks |
I'll close this one today.
Le mer. 15 mai 2024, 12 h 14 a.m., Hello World ***@***.***> a
écrit :
… @wuwentao <https://github.com/wuwentao> @CyrielRct
<https://github.com/CyrielRct> which repo fork should we try to start
using? :) AFAISaw @wuwentao <https://github.com/wuwentao> has already
initiated the process of removing the unmaintained repo from HACS and add
his fork to HACS. Should we use that repo?
Ps: really open if I can be of any help. I'm a dev with GH experience :)
Hi @daniel-toth-leeder <https://github.com/daniel-toth-leeder>
please use my fork to do the future changes, and I will continue maintain
it now.
as I can fully control all the project setting and make changes quickly,
I'm using github projects in my daily work.
in additional, I will add more people to collaborator list once they
submit more PRs later, they will have permission to merge PR in future.
and NOT keep all the merge PR permission in one people.
Thanks
Wentao
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6Z5DMSAP3SCYUSEJVEXN3ZCLOLTAVCNFSM6AAAAABHJTWC62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJRGU2DONJZGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The hacs recommended validation jobs are already configured in this repository just not enabled. It might be a good idea to enable it and maybe also configure some sane and free security checks.
The text was updated successfully, but these errors were encountered: