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

Impossible to apply with atlantis/apply status explicitly checked #811

Closed
qugu opened this issue Oct 22, 2019 · 1 comment
Closed

Impossible to apply with atlantis/apply status explicitly checked #811

qugu opened this issue Oct 22, 2019 · 1 comment
Labels
duplicate This issue is a duplicate of an already reported issue

Comments

@qugu
Copy link

qugu commented Oct 22, 2019

This may be related to #453

Running the latest Atlantis from the docker image as per today, Oct 22. Running on a GitHub, with protected branches enabled. The status checks have atlantis/plan and atlantis/apply checked.

Issue
When trying to apply after a successful plan, I get an error message: "Apply Failed: Pull request must be mergeable before running apply.". PR changes can neither be applied nor merged.

Expected behavior
Apply succeeds and only then the PR can be merged.

For the sake of test, the PR is approved. This looks like this:

Screenshot 2019-10-22 at 17 57 11

If the checkmark for atlantis/apply is removed, I can apply successfully, but also merge without applying (which is undesired).

My configuration JSON passed to atlantis:

{
    "repos": [
        {
            "id": "/.*/",
            "apply_requirements": [
                "mergeable",
                "approved"
            ],
            "allowed_overrides": [
                "workflow"
            ],
            "allow_custom_workflows": true
        }
    ]
}
@qugu
Copy link
Author

qugu commented Oct 23, 2019

Sorry, this is a duplicate of #523

@qugu qugu closed this as completed Oct 23, 2019
@lkysow lkysow added the duplicate This issue is a duplicate of an already reported issue label Oct 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue is a duplicate of an already reported issue
Projects
None yet
Development

No branches or pull requests

2 participants