Put your pull request into the merge queue.
queue action allows you to put a pull request into a merge
queue. By placing pull requests in a queue, you can make sure
they are up-to-date and control their processing based on their priority.
|Key name||Value type||Default|
This option is relevant only if you do inplace checks and if you use the
Template to use as the commit message when using the
Mergify can impersonate a GitHub user to merge pull requests. If no
Merge method to use. If no value is set, Mergify will use the first authorized method available in the repository configuration.
The name of the queue where the pull request should be added. If no name is set,
To set your priorities, you should now use
Allow merging Mergify configuration change.
Whether branch protections are required for queueing pull requests.
For certain actions, such as rebasing branches, Mergify has to impersonate a GitHub user. You can specify the account to use with this option. If no
This option overrides the value defined in the queue rules section of the configuration.
Method to use to update the pull request with its base branch when the speculative check is done in-place. Possible values:
pull_request_rules:- name: put PRs in queueconditions:- base=mainactions:queue:
In this example, any pull request that is based on the main branch will be
placed in the production queue. The pull request still needs to match the
queue_conditions defined in the queue to enter the queue.
pull_request_rules:- name: put PRs in queue (rebase)conditions:- base=main- label=rebaseactions:queue:merge_method: rebase- name: put PRs in queue (merge)conditions:- base=main- label!=rebaseactions:queue:merge_method: merge
In this example, any pull request that has the label
rebase will enter the
queue with a
merge_method set to
rebase, ensuring it's merged via rebase.
Whereas all the other pull requests will be merged using the