Edit HEAD of a PR to associate with another branch

[AdamMajer]

Feature Description

In a typical workflow,

1. do some changes on branch foo
2. create a PR
3. add some commits to branch foo
4. PR is updated

Now, how can I turn this automatic branch following off?

The reason is specific workflows that can run long time and where changes on the source branch may not be wanted in the PR.

In the API https://demo.gitea.com/api/swagger/#/repository/repoEditPullRequest I can't set the HEAD branch to another branch. The other branch could even refer to same commitid.

Screenshots

No response

[wxiaoguang]

The reason is specific workflows that can run long time and where changes on the source branch may not be wanted in the PR.

It sounds like something "skip ci"?

[AdamMajer]

It's not about CI. It's more analogous to merging from a devel branch to a stable branch when maintainer of the stable branch likes it. But instead of creating a new label, they just do a PR from devel -> stable.

I guess a workaround could be to close the original PR and replace it with another where the commit id is on a "PR_to_stable" branch and not devel branch itself. But it would be nice to be able to do this via API, and "retarget" the source of the PR to specific commit id.

[wxiaoguang]

Hmm, I think it's almost impossible at the moment. The PR system's design is "a PR always follows its branch", this mechanism is widely used everywhere in code.

[AdamMajer]

That's fine, but it would be nice to be able to at least retarget to a different source branch name that the tooling creates.

[AdamMajer]

I see that this requires branches everywhere. So, having ability to reset the branch to different branch would be sufficient here.