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

Gitea 1.17.0 ignores "Default merge style for pull requests" #20562

Closed
achikhv opened this issue Jul 31, 2022 · 3 comments · Fixed by #20564
Closed

Gitea 1.17.0 ignores "Default merge style for pull requests" #20562

achikhv opened this issue Jul 31, 2022 · 3 comments · Fixed by #20564
Labels

Comments

@achikhv
Copy link

achikhv commented Jul 31, 2022

Description

Gitea 1.17.0 ignores "Default merge style for pull requests:" for repository and always shows "Create merge commit". My repositories are configured to squash-merge by default, and after update from 1.16.9 to 1.17.0 default button is again merge commit.

URL of Gitea demo: https://try.gitea.io/achi/test/pulls/1
It shows "Create merge commit", but repository's setting is "Create squash commit".

Gitea Version

1.17.0

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

Not relevant

Operating System

Windows

How are you running Gitea?

Used "https://dl.gitea.io/gitea/1.17.0/gitea-1.17.0-windows-4.0-amd64.exe"

Database

MSSQL

@wxiaoguang
Copy link
Contributor

wxiaoguang commented Jul 31, 2022

Sorry, I forgot to choose the default merge style.

Will be fixed by #20564 (for 1.18)

Once the backport #20565 is merged (and finishes the build), you can use the latest 1.17 binary (https://dl.gitea.io/gitea/1.17) or latest 1.17 docker image (1.17-dev) to get this fix.

@viceice
Copy link
Contributor

viceice commented Aug 1, 2022

@wxiaoguang When do you think this fix will be released in v1.17.1?

@wxiaoguang
Copy link
Contributor

I am not sure. It depends when the owners/maintainers decide to make a new release. Maybe (usually) a week later?

I think you can use the latest 1.17 binary (https://dl.gitea.io/gitea/1.17) or latest 1.17 docker image (1.17-dev) to get this fix. They are as stable as 1.17 and contain all bug fixes for next unreleased 1.17.x

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants