Skip to content

Commit b663d15

Browse files
authored
add note on mergability check (#1900)
1 parent be4f65a commit b663d15

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

docs/ce/howto/apply-requirements.mdx

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,3 +8,22 @@ Digger currently does not support `apply_requirements` (like in Atlantis). Comin
88

99
You can use mergeability requirements together with Status Checks to achieve the same.
1010
Digger will not apply if the pull request is not in a “mergeable” state as specified by GitHub api. This means that if you have a separate status check and you have this check as “required” by branch protection rules then an attempt of digger apply will not go ahead.
11+
12+
Note: there is a [known issue](https://github.com/diggerhq/digger/issues/1180) that would
13+
cause the "mergability" check to conflict if you set the digger/apply check as required on github. We are working on a fix and in the meantime you have an option to turn off the mergability check if you want to have this digger/apply check as required. You can turn it off in the workflow configuration
14+
by setting the `skip_merge_check` flag as follows (we have to set the other configurations since they are currently required):
15+
16+
```
17+
projects:
18+
- name: dev
19+
dir: dev
20+
workflow: mydev
21+
22+
workflows:
23+
mydev:
24+
workflow_configuration:
25+
on_pull_request_pushed: ["digger plan"]
26+
on_pull_request_closed: ["digger unlock"]
27+
on_commit_to_default: ["digger unlock"]
28+
skip_merge_check: true
29+
```

0 commit comments

Comments
 (0)