Post Check (Deprecated)

Merge Protections replace post_check by letting you define success_conditions directly, without creating an intermediate check-run.

pull_request_rules:
  - name: Check CI status
    conditions:
      - base=main
    actions:
      post_check:
        success_conditions:
          - check-success=ci/test
        neutral_conditions:
          - check-neutral=ci/lint
        title: "Mergify check: {{ check_rule_name }}"
        summary: |
          {{ check_conditions }}

merge_protections:
  - name: Check CI status
    if:
      - base=main
    success_conditions:
      - or:
          - check-success=ci/test
          - check-neutral=ci/lint

The post_check action allows Mergify to create a check-run on a pull request. This can be useful in situations where you want to add a custom check to the status of a pull request based on Mergify’s evaluation.

As the title and summary are templates, you can benefit from any pull request attributes, e.g. {{author}}, and also these additional variables:

• {{ check_rule_name }} the name of the rule that triggered this action;

• {{ check_status }} the resulting check-run status: success when the success_conditions match, neutral when the neutral_conditions match, and failure otherwise. When neither option is set, the triggering rule’s own conditions decide between success and failure;

• {{ check_succeeded }} is true if check_status is success, false otherwise;

• {{ check_conditions }} the success_conditions with a checkbox marked against each one that matches. It is empty when only neutral_conditions is set, and falls back to the triggering rule’s own conditions when neither option is set.

{{ check_succeed }} is also available as an alias of {{ check_succeeded }}, kept for backward compatibility.