Feature request: Change destination of PR #4284

New Issue

GiteaMirror · 2025-11-02T05:44:47-06:00

GiteaMirror commented

2025-11-02 05:44:47 -06:00

Originally created by @neunzehnachtneun on GitHub (Nov 11, 2019).

Just in short, I would really appreciate a feature to change the destination of an existing pull request, like Bitbucket has implemented.

Thanks in advance.

If this feature already exists, please someone could explain how to do. I didn't find it. Neither in the docs nor by try-and-error.

Originally created by @neunzehnachtneun on GitHub (Nov 11, 2019). Just in short, I would really appreciate a feature to change the destination of an existing pull request, like Bitbucket has implemented. Thanks in advance. If this feature already exists, please someone could explain how to do. I didn't find it. Neither in the docs nor by try-and-error.

GiteaMirror closed this issue

2025-11-02 05:44:48 -06:00

GiteaMirror commented

2025-11-02 05:44:48 -06:00

@guillep2k commented on GitHub (Nov 11, 2019):

You mean the target repository/target branch? That would invalidate the PR comments and reviews. What's the point, if it's much easier to create a new PR from the same branch?

@guillep2k commented on GitHub (Nov 11, 2019): You mean the target repository/target branch? That would invalidate the PR comments and reviews. What's the point, if it's much easier to create a new PR from the same branch?

GiteaMirror commented

2025-11-02 05:44:49 -06:00

@neunzehnachtneun commented on GitHub (Nov 11, 2019):

Well thanks for intervening, I just thought from my use case. I a small project we just decided to merge no longer into master generally but into the develop branch. So a few open PRs need either a destination update or we have to create new PRs based on the old ones. In this specific case this feature would be really useful, as the comments and reviews stay valid.
But in general I totaly agree, to reject this idea.

@neunzehnachtneun commented on GitHub (Nov 11, 2019): Well thanks for intervening, I just thought from my use case. I a small project we just decided to merge no longer into master generally but into the develop branch. So a few open PRs need either a destination update or we have to create new PRs based on the old ones. In this specific case this feature would be really useful, as the comments and reviews stay valid. But in general I totaly agree, to reject this idea.

GiteaMirror commented

2025-11-02 05:44:49 -06:00

@guillep2k commented on GitHub (Nov 11, 2019):

As a "once only" workaround you could try updating the pull_request table (make a backup first!) changing the base_branch column to your needs. Make sure to use the index column to refer to PR numbers, since the ID is an internal value and not what you see in the UI.

@guillep2k commented on GitHub (Nov 11, 2019): As a "once only" workaround you could try updating the pull_request table (make a backup first!) changing the base_branch column to your needs. Make sure to use the index column to refer to PR numbers, since the ID is an internal value and not what you see in the UI.

GiteaMirror commented

2025-11-02 05:44:49 -06:00

@neunzehnachtneun commented on GitHub (Nov 12, 2019):

Oh, thanks. This is really helpful.
I will close this issue, as you are right, there are no real use cases for this feature.

@neunzehnachtneun commented on GitHub (Nov 12, 2019): Oh, thanks. This is really helpful. I will close this issue, as you are right, there are no real use cases for this feature.

GiteaMirror referenced this issue

2025-11-02 12:32:25 -06:00

[PR #4284] [MERGED] Keep preseeded database password #17316

GiteaMirror referenced this issue

2025-11-02 14:02:05 -06:00

[PR #4932] [CLOSED] fix bug forget to remove Stopwatch when remove repository #17555

Sign in to join this conversation.