Forked Repo PR Blocked — New developer cannot set "Ready for Review" and PR stuck in Draft due to author leaving organization

Hi,
We are facing an issue with a forked repository created from https://github.com/home-assistant/core under our organization.

The original developer who opened the pull request is no longer with the company, and the task has been reassigned to another developer. However, the new developer is unable to mark the PR as “Ready for Review” due to permission limitations.

We did not anticipate the review process taking this long, and we are now stuck.

If we create a new pull request that includes all the requested changes and fixes from the original PR, will it be treated with the same priority, or will it go through the full review process again?

Original PR request: https://github.com/home-assistant/core/pull/158511

Regards,
Syeda Farwa
Cloud Manager
Cielo WiGle Inc.

Hello :wave:,

thanks for reaching out. Our review queue is quite big so it takes longer indeed.

So for this PR I think I was almost done reviewing it as I have already started with the tests. I will give it another pass after writing this, and if it’s good we can merge it and you can start improving the integration with your own account (don’t worry, the PRs following are smaller and thus are generally easier to review and easier to merge).

If I still find stuff, feel free to message me on Discord. Like said, I started with the tests so it shouldn’t take long now.

In theory the PR could be reopened, but at this point we have the full history in the current PR, so might as well stick with this one (if this was the start of the process I would probably recommend to reopen, but this is almost done).

Hope to have answered your questions!

Kind regards,

Joost Lekkerkerker