Skip to content

Skipped checks on automerge are falsly considered successful  #3649

Open
@evantahler

Description

@evantahler

We've got classic branch protections enabled on our main branch.

Screenshot 2025-01-11 at 11 14 00 AM

Our test suite is set up such that a number of sub-jobs need all pass which then trigger a final job, backend-test-complete, which is the required check in the branch protection.

jobs: 

...

  backend-test-complete:
    runs-on: ubuntu-latest
    needs:
      - backend-lint
      - backend-seed
      - backend-tests
      - backend-acceptance-tests
    steps:
      - run: echo "SUCCESS!"

If one of the sub jobs fails (in this example, backend-seed), the final job, backend-test-complete is skipped.

Screenshot 2025-01-11 at 11 16 14 AM Screenshot 2025-01-11 at 11 17 05 AM

However, auto-merge proceeded when it should have been prevented. The language about branch protections implies that "skipped" jobs should not pass the branch protection, and only "successful" jobs should pass:

Screenshot 2025-01-11 at 11 10 54 AM

So... I think it is a bug that automerge happened in this case. Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions