This pull request cannot be embarked for merge

[andrewhsu]

I've configured the free plan of mergify on a test repo to try out some merge queue scenarios. Specifically, I'm trying to see how mergify performs rebase to keep a PR up-to-date with its base branch instead of merge.

I have the following .mergify.yml file:

queue_rules:
  - name: default
    allow_inplace_checks: true
    conditions:
      - check-success=render
      - check-success=Lint go files
      - check-success=Lint python files
      - check-success=Lint shell scripts
      - check-success=Run tests (linux, amd64)
pull_request_rules:
  - name: merge using the merge queue
    conditions:
      - "#approved-reviews-by>=1"
      - check-success=render
      - check-success=Lint go files
      - check-success=Lint python files
      - check-success=Lint shell scripts
    actions:
      label:
        add:
          - queued
      queue:
        name: default
        method: rebase
        update_method: rebase

However, when I send the command via github comment:

@Mergifyio queue

It fails to add the PR to the queue with the following check failure, even though i can login to the mergify dashboard with andrewhsu:

Am I missing some other configuration step to allow mergify to perform this action?

[sileht]

We took a look, this is a GitHub permission model limitation.

The token issued by GitHub allows Mergify to act on behalf of andrewhsy on 5g6g/red-panda repository and the pull request branch of any forked repository if the author allows maintainers to edit the pull request.

Unfortunately, in your case, andrewhsy/red-panda is not a fork of 5g6g/red-panda, so GitHub doesn't allow Mergify to edit the pull request.

Note: in your case 5g6g/red-panda is a fork andrewhsy/red-panda, not the reverse.

If your fork setup were the other way around, Mergify would have worked as you expected.

On our side, we plan to improve the error message in such a case.