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

Scheduling an auto-merge no longer works in 1.18.4 #23022

Closed
parnic-sks opened this issue Feb 20, 2023 · 6 comments
Closed

Scheduling an auto-merge no longer works in 1.18.4 #23022

parnic-sks opened this issue Feb 20, 2023 · 6 comments
Labels
Milestone

Comments

@parnic-sks
Copy link

Description

The "auto-merge when checks succeed" feature was working in 1.18.3, but in 1.18.4, users receive

This pull request is not ready to be merged, check review status and status checks.

Same error message is being seen in #23000 but this is a non-admin scenario, so I thought it probably deserved its own issue.

This is not reproducing on try.gitea.io, but on try, I don't see the auto-merge feature at all, so maybe I'm doing something wrong.

Gitea Version

1.18.4

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

image

image

image

Git Version

2.39.1

Operating System

Ubuntu 20.04.3, aarch64/arm64

How are you running Gitea?

Self-built from 1.18.4 tag with an additional fix to LFS downloads.

Database

PostgreSQL

@wxiaoguang
Copy link
Contributor

The biggest (and somewhat related) PR between 1.18.3 and 1.18.4 is #22812 @zeripath do you have a time to take a look?

@wxiaoguang
Copy link
Contributor

OK, I think I understand the problem now.

It's the same problem as #23000 , the problem is that there were bugs on bug, which made the old code happened to work.

When the "force checking" bug was fixed by #22812, other bugs came.

To fix other bugs, I think the code should be like:

skipProtectionCheck := force || auto

CheckPullMergable( ..., skipProtectionCheck bool)

A fix is on the way.

@lunny lunny added this to the 1.18.5 milestone Feb 21, 2023
@zeripath
Copy link
Contributor

Ah bugs that are hidden due to other bugs - the gift that keeps on giving.

I think this clearly indicates we need some tests for the automerge capability - however, that may mean that it needs some restructuring in order to make it testable.

@lunny
Copy link
Member

lunny commented Feb 21, 2023

I think we need to redesign the automerge, we need a queue like what Github did.

@lunny
Copy link
Member

lunny commented Feb 21, 2023

Isn't this fixed by #23010 ?

@zeripath
Copy link
Contributor

yup Fixed by #23010

@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants