GitLab MRs should be "Mergeable" if jobs are skipped or (only) Atlantis job failed

[carlbordum]

Based off #2137 and @Skeen 's work. Also makes MR's mergable if commit statuses are skipped. This makes Atlantis much more suitable with monorepos, where you sometimes only run some tests (ie skip other jobs) based on the changes.

[michelmzs]

Hi @carlbordum, could you explain a situation where a skipped job blocks the Atlantis workflow?

[carlbordum]

Take this example from the Gitlab CI documentation where they only want to run docker build when the Dockerfile changes (ofc this is strange, but fine for the example).

In this case, currently atlantis will not be able to apply because the CI job is not successful (its just skipped) and therefore we always have to run every job. This wastes a lot of time for developers as we are using a monorepo.

Hope it makes sense

[jamengual]

@carlbordum Please add tests, thanks.

[michelmzs]

Take this example from the Gitlab CI documentation where they only want to run docker build when the Dockerfile changes (ofc this is strange, but fine for the example).

In this case, currently atlantis will not be able to apply because the CI job is not successful (its just skipped) and therefore we always have to run every job. This wastes a lot of time for developers as we are using a monorepo.

Hope it makes sense

Are you sure that the current implementation will look for other status besides the external stage created by the Atlantis itself? I'm guessing that it won't block the workflow, I need to test.

[carlbordum]

@jamengual sorry I will not use more time on this, feel free to close.

Yes @michelmzs, all ci jobs need to pass, maybe its the way we set Atlantis up.