7.7.0

New Features

• A new action called github_actions has been added, which allows to dispatch your GitHub Workflows. Each dispatched workflow can receive inputs used in the workflow job run to be dispatched.
• Mergify now includes a new queue rules attribute branch_protection_injection_mode, allowing to set several different modes of injection for branch protections in the merge queue (see documentation for further information)
• Added queue-dequeue-reason condition.
• A new current-datetime condition allows triggering a rule depending on a specific date/time.
• The attributes added-files, modifed-files and removed-files have been added.
• Add new /repos/{owner}/{repository}/logs endpoint to the API. This endpoint returns the Mergify event logs of a repository.
• There is a new unqueue reason for branch update failure that you can use with the queue-dequeue-reason condition.
• There are new unqueue reasons for conflicts with the base branch or conflicts with a pull request ahead in queue that you can use with the queue-dequeue-reason condition.
• The YAML object at the end of the body of draft PR pull requests now contains information about previous failed batches. The new data is in a new key called previous_failed_batches which is a list of dict objects containing the number of the draft pr (under the draft_pr_number key) and the list of pull requests it checked (under the checked_pull_requests key). Example:

previous_failed_batches:
- draft_pr_number: 130
  checked_pull_requests:
  - 123
  - 124
  - 126

• The requeue command has been improved: when used it will now automatically queue the pull request again, only if you do not have any queue action in your pull_request_rules. This allows to clean the failed queued state of the pull request and queue it again with only a single command. To go with this improved behavior, the requeue command also has a new, optional, queue-name parameter. It allows you to specify the queue name in which you want to requeue the pull request, eg: @Mergifyio requeue default
• Conditions of type Timestamp intervals in the configuration now support unspecified digits.

Deprecation Notes

• The require_branch_protection option is being deprecated. It is now replaced by the queue_rules option branch_protection_injection_mode. The option will be removed in 8.0.0.
• The following API endpoints are deprecated and will be removed in a month :
• /repos/{owner}/{repository}/pulls/{pull}/events
• /repos/{owner}/{repository}/events

They are replaced by the already functional :

/repos/{owner}/{repository}/logs