Skip to content

POST /repos/{owner}/{repo}/pulls/{index}/merge with fast-forward-only don't respect merge_when_checks_succeed #35756

@ZBSTooling

Description

@ZBSTooling

Description

When the repository is configured with only one Merge-Style 'fast-forward-only' and renovate creates autoMerge Requests with the following payload the PR is fast-forwarded immediatley without waiting for successfull status checks.

{ "Do": "fast-forward-only", "delete_branch_after_merge": true, "merge_when_checks_succeed": true }

Gitea Version

1.24.7

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Gitea is running with docker-compose

Database

PostgreSQL

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions