Thanks to visit codestin.com
Credit goes to github.com

Skip to content

CI Bug: Invalid GitHub merge queue configurations #1312

@chaoticlonghair

Description

@chaoticlonghair

Contact Details

No response

Current Behavior

A PR, which will break CI, could be merged with GitHub merge queue.

For example:

Expected Behavior

From the official GitHub Docs, we can find the follow description:

The merge queue provides the same benefits as the Require branches to be up to date before merging branch protection,

With the correct use of GitHub merge queue, we should have "the same benefits" as "to be up to date".

Otherwise, why we don't just click the "merge" button to merge PR directly?

OS

Not Associated

Axon version

No response

Kernel

Not Associated

Relevant log output

No response

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    t:bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions