Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rebase and Fast-forward for Pull-Request is not working properly #25177

Closed
jim-kirisame opened this issue Jun 9, 2023 · 3 comments · Fixed by #25779
Closed

Rebase and Fast-forward for Pull-Request is not working properly #25177

jim-kirisame opened this issue Jun 9, 2023 · 3 comments · Fixed by #25779
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Milestone

Comments

@jim-kirisame
Copy link
Contributor

Description

Hi, I'm notice the "Rebase and Fast forward" mode for Pull Requst is not work properly in 1.20.0-rc0. It will modify the last commit of the PR and rewrite the message of commit to "Merge pull request 'xxx' (#1) from BRANCH into main"

I have reproduce the bug in try.gitea.io. This is the link:

The HEAD of PR branch is 30a8edb4 but in main branch is 29420402, which is not correct in Rebase and Fast-forward mode.

Gitea Version

1.20.0-rc0, or 1.20.0+rc0-17-g81211db07

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

https://try.gitea.io/

Database

None

@jim-kirisame jim-kirisame changed the title Rebase and Fast-forward for Pulll-Request is not working properly Rebase and Fast-forward for Pull-Request is not working properly Jun 9, 2023
@eremenko789
Copy link

Still relevant for 1.20.0-rc2

@mmithril
Copy link

mmithril commented Jul 3, 2023

Possible workaround: use Squash commit & edit the message manually.

Please fix as soon as possible anyway.

@wxiaoguang wxiaoguang added this to the 1.20.0 milestone Jul 3, 2023
@wxiaoguang wxiaoguang added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Jul 3, 2023
@wxiaoguang
Copy link
Contributor

-> Avoid amending the Rebase and Fast-forward merge if there is no message template #25779

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants