+1 for this.

I created a draft PR for a proof-of-concept a while back, and today one of my teammates finished the job. He put in much more work than I did, and then published the PR, and I can't approve it.

There are a bunch of questions on stackoverflow about this kind of thing. The workaround is to open a new PR, but then you lose any comments and approvals from the original PR.

https://stackoverflow.com/questions/66539231/how-to-change-the-owner-of-a-pr-on-github-how-to-commandeer-an-open-github-pr

https://stackoverflow.com/questions/50781553/how-to-take-ownership-of-a-pull-request

+1

I reverted a change, I restored the branch, and I made a new PR to make my developer's life easier, but now he's going to write the fix and I'm supposed to review it and can't because I own it. It would be nice if I could edit the PR author field. I understand how this could be abused to allow me to review my own PRs, but assuming the second developer has to accept the invitation to be the new author this could be avoided.

+1

I started with a minor change made by a teammate but it became clear that much more work was required to actually deliver on the goal. The original teammate left for vacation and handed that work off to me. After completing my changes I discovered that I had the power to review and merge it myself (I didn't do it) even though almost 100% of the code was mine. I shouldn't have that ability.

+1 on this

can we expect this feature anytime in the near future?

Our team would also find this very useful.

• 1

+1 for this. I think this is useful because we could have someone drop a pull request for some reason and needing someone to continue doing it, without losing comments or reviews. And also not allowing, as a consequence, the new author to approve it's own PR (since in the current version it's technically not theirs)

+1

+1

+1. Phab-style commandeering would be very helpful!

+1

+1

+1

+1 happy 2025

+1

+1

+1

+1

+1

+1

+1

++

+1

+1

+1