Transfer PR authorship #13868

New Issue

GiteaMirror · 2025-11-02T10:55:35-06:00

GiteaMirror commented

2025-11-02 10:55:35 -06:00

Originally created by @jpraet on GitHub (Dec 21, 2024).

Feature Description

It would be useful if the author of a PR could transfer the PR to another author.

It is not uncommon for PR's to be handed over to be completed by another developer.
When that happens, there are currently some problems:

the new developer that is working on the PR can now approve his own work, this is not right
the original author of the PR cannot approve / reject the PR, even though it's not really theirs anymore

See also related discussion https://github.com/orgs/community/discussions/15067

Screenshots

No response

Originally created by @jpraet on GitHub (Dec 21, 2024). ### Feature Description It would be useful if the author of a PR could transfer the PR to another author. It is not uncommon for PR's to be handed over to be completed by another developer. When that happens, there are currently some problems: * the new developer that is working on the PR can now approve his own work, this is not right * the original author of the PR cannot approve / reject the PR, even though it's not really theirs anymore See also related discussion https://github.com/orgs/community/discussions/15067 ### Screenshots _No response_

GiteaMirror added the topic/pr type/proposal labels 2025-11-02 10:55:35 -06:00

GiteaMirror commented

2025-11-02 10:55:36 -06:00

@wxiaoguang commented on GitHub (Dec 21, 2024):

It sounds a good feature but it is very difficult to make it completely right with some simple approaches, I can see a lot of edge cases.

IMO the clearest workflow should be "close the old one and let the new author start a new one".

@wxiaoguang commented on GitHub (Dec 21, 2024): It sounds a good feature but it is very difficult to make it completely right with some simple approaches, I can see a lot of edge cases. IMO the clearest workflow should be "close the old one and let the new author start a new one".

GiteaMirror commented

2025-11-02 10:55:36 -06:00

@lunny commented on GitHub (Dec 21, 2024):

If the head branch came from a fork repo, the new author may have no permission to push code

@lunny commented on GitHub (Dec 21, 2024): If the head branch came from a fork repo, the new author may have no permission to push code

GiteaMirror commented

2025-11-02 10:55:36 -06:00

@GiteaBot commented on GitHub (Jan 21, 2025):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Jan 21, 2025): We close issues that need feedback from the author if there were no new comments for a month. :tea:

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13868