"Update Branch" button on PR #4641

New Issue

GiteaMirror · 2025-11-02T05:57:07-06:00

GiteaMirror commented

2025-11-02 05:57:07 -06:00

Originally created by @techknowlogick on GitHub (Jan 13, 2020).

Related #8659

Similar to GitHub when a branch on a PR is out of sync, then an "Updated Branch" button could be used to merge commits from upstream into PR branch (assuming no merge conflicts)

Originally created by @techknowlogick on GitHub (Jan 13, 2020). Related #8659 Similar to GitHub when a branch on a PR is out of sync, then an "Updated Branch" button could be used to merge commits from upstream into PR branch (assuming no merge conflicts)

GiteaMirror added the type/enhancement label 2025-11-02 05:57:07 -06:00

GiteaMirror closed this issue

2025-11-02 05:57:07 -06:00

GiteaMirror commented

2025-11-02 05:57:08 -06:00

@techknowlogick commented on GitHub (Jan 13, 2020):

I've just placed a bounty on this issue: https://www.bountysource.com/issues/86919260-update-branch-button-on-pr

@techknowlogick commented on GitHub (Jan 13, 2020): I've just placed a bounty on this issue: https://www.bountysource.com/issues/86919260-update-branch-button-on-pr

GiteaMirror commented

2025-11-02 05:57:08 -06:00

@zeripath commented on GitHub (Jan 13, 2020):

An extension that would also be needed is to make the author suggestions ignore these merge commits too.

@zeripath commented on GitHub (Jan 13, 2020): An extension that would also be needed is to make the author suggestions ignore these merge commits too.

GiteaMirror commented

2025-11-02 05:57:08 -06:00

@davidsvantesson commented on GitHub (Jan 14, 2020):

Maybe all commits which is merge from target shall be ignored as authors, even if not done in UI?

@davidsvantesson commented on GitHub (Jan 14, 2020): Maybe all commits which is merge from target shall be ignored as authors, even if not done in UI?

GiteaMirror commented

2025-11-02 05:57:09 -06:00

@zeripath commented on GitHub (Jan 14, 2020):

Exactly!

@zeripath commented on GitHub (Jan 14, 2020): Exactly!

GiteaMirror commented

2025-11-02 05:57:09 -06:00

@davidsvantesson commented on GitHub (Jan 15, 2020):

Maybe something to add in the future:
https://github.com/isaacs/github/issues/1419

@davidsvantesson commented on GitHub (Jan 15, 2020): Maybe something to add in the future: https://github.com/isaacs/github/issues/1419

GiteaMirror commented

2025-11-02 05:57:09 -06:00

@6543 commented on GitHub (Jan 16, 2020):

working on it .. to https://github.com/isaacs/github/issues/1419 I plan to reuse a lot of the normal merge code ... so to extend the function should be easy (but I like get the a simple PR in first, extend afterwards)

@6543 commented on GitHub (Jan 16, 2020): working on it .. to https://github.com/isaacs/github/issues/1419 I plan to reuse a lot of the normal merge code ... so to extend the function should be easy (but I like get the a simple PR in first, extend afterwards)

GiteaMirror commented

2025-11-02 05:57:10 -06:00

@akostin33 commented on GitHub (May 13, 2020):

working on it .. to isaacs/github#1419 I plan to reuse a lot of the normal merge code ... so to extend the function should be easy (but I like get the a simple PR in first, extend afterwards)

Could you please attach the link to issue in gitea project same as isaacs/github#1419 ?

@akostin33 commented on GitHub (May 13, 2020): > working on it .. to [isaacs/github#1419](https://github.com/isaacs/github/issues/1419) I plan to reuse a lot of the normal merge code ... so to extend the function should be easy (but I like get the a simple PR in first, extend afterwards) Could you please attach the link to issue in gitea project same as [isaacs/github#1419](https://github.com/isaacs/github/issues/1419) ?

GiteaMirror commented

2025-11-02 05:57:10 -06:00

@6543 commented on GitHub (May 13, 2020):

@akostin33 created #11401

and status update: didnt looked into it at the moment ... to many things

@6543 commented on GitHub (May 13, 2020): @akostin33 created #11401 and status update: didnt looked into it at the moment ... to many things

GiteaMirror referenced this issue

2025-11-02 13:25:31 -06:00

[PR #4641] [CLOSED] MySQL TLS #17443

Sign in to join this conversation.