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.

Sign up for GitHub

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

docs: document not operator #6108

Merged
merged 1 commit into from
Mar 4, 2025
Merged

docs: document not operator #6108

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions src/content/docs/configuration/conditions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -358,6 +358,28 @@ reviews or if the `test job` check passes.
Combining conditions using logical operators can help you create more
sophisticated rules tailored to your repository's workflow and requirements.

### The `not` Operator

The `not` operator is used to negate a block of conditions such that if a
condition is true, it becomes false. In Mergify rules, the `not` operator is
represented by using the `not` keyword and specifying the underlying condition
block with `or` or `and`.

Example

```yaml
pull_request_rules:
- name: Merge when both condition are not met
conditions:
- not:
and:
- "#approved-reviews-by >= 2"
- "check-success = test job"
actions:
merge:
method: merge
```

## Testing and Debugging Conditions

When crafting conditions for your Mergify rules, it's essential to test and
Expand Down
Loading