FIrst try to add issue template

[ultratoto14]

As I do not have the rights to use the repository workflow, trying in that way.

[postlund]

I suggest that you add bug here.

[ultratoto14]

I was thinking about it, but as for the moment, we do not have a feature_request template, or a new_device template, should we do it know or automatically categorize once we have different templates ?

[postlund]

Good point. Maybe we should just grab the bull by the horns and fix all of them? I have a few in my pyatv repo that has worked pretty well (for inspiration):

https://github.com/postlund/pyatv/tree/master/.github/ISSUE_TEMPLATE

[CloCkWeRX]

I had a go at a PR template in #782

[postlund]

@rospogrigio I suggest that you make me and/or @ultratoto14 admins so we can steer the ship until you have time. That way you can just forget about localtuya until a better point in time.

[rospogrigio]

@rospogrigio I suggest that you make me and/or @ultratoto14 admins so we can steer the ship until you have time. That way you can just forget about localtuya until a better point in time.

Yeah, totally agree: as I said from the very beginning it was just a matter of time until you'd better take over.
Doing it now, I am quite overwhelmed these days...

Edit: wait... how am I supposed to do that??

[ultratoto14]

@rospogrigio maybe in Settings -> Manage Access

[rospogrigio]

You are already listes as Collaborators, and there is no "Admin" options:

[postlund]

My bad, I was under the impression that the access levels were more fine grained that they are. Only the repository owner has super user power and there can only be one owner. Collaborators can't get the kind of permissions needed I'm afraid.

[ultratoto14]

@rospogrigio if you want @postlund to take the lead on this repository, it seems the only way is to transfer the ownership

Seems that fine grained rights tuning is only for github enterprise.

[rospogrigio]

OK then, just one question: what will happen with the HACS integration? It is enlisted as rospogrigio/localtuya there, as far as I remember...

[ultratoto14]

@rospogrigio i created an empty repository and transfer you the ownership, will see, maybe you need to accept.

[rospogrigio]

@ultratoto14 Can't see it...
Edit: saw it, and accepted.

[ultratoto14]

@rospogrigio the repository https://github.com/ultratoto14/TestingRepository
In the settings, i currently have

[ultratoto14]

Yes, so it renamed the repository ... f.ck

[rospogrigio]

So, I suggest we investigate if there will be any issue with HACS, or if renaming the ownership can be transferred easily...

[ultratoto14]

By the way, it seems that the PR is working, tested it on my own repo.

[postlund]

I guess we can transfer ownership and you immediately make a new fork of it @rospogrigio. That way HACS can point to the fork until we have updated the repo in HACS.

[rospogrigio]

It tells me that "postlund already has a repository in the mileperhour/localtuya-homeassistant network".

[ultratoto14]

If the repository is changed then all the users will also have to update their links.

[postlund]

I have removed my local fork now, so hopefully it should work. Tried to read up a bit and I think all previous references will still work. So if anyone tries to use the old addresses, they will automatically point towards my repo, which means we are fine. People should still update to the new address though, we included when it comes to HACS.

[rospogrigio]

@postlund repository transfer requested :wink ... oops I transferred it to the trout!!! 🤣
Edit: do you confirm that I am supposed to make a new fork of the repo once you've accepted?

[postlund]

@rospogrigio I am suppose to confirm, but maybe we should take another route instead. There's an organization for custom components here:

https://github.com/custom-components

I'm sort of taking ownership of the remote_homeassistant component as well and we will move it to that organization. Maybe that's a better way to deal with this as well?

[postlund]

Let's merge this and see what happens...