Priority Merges

Find out how the priority merge feature works. When this label is applied to a pull request, Aviator moves it to the front of the queue to be merged first.

At times there are high priority changes that cannot wait for all the pull requests ahead of this change in the queue. With Aviator, you can handle this by applying a skip_line label. When this label is applied to a pull request, Aviator will move this pull request to the front of the queue to be merged first.

Customizing the label

The default skip_line label is mergequeue-priority. This label can also be customized via merge_rules.labels in the YAML config:

merge_rules:
  labels:
    trigger: "label_name"
    skip_line: "skip_line"

Priority in parallel mode

When a skip_line label is applied in a repository using the parallel queue mode, all pending bot pull requests are also closed and new bot pull requests are constructed. Read more about this in our parallel mode documentation. The behavior is also similar when using fast-forwarding or when using batching.

Priority when using affected targets

When using affected targets, only the pull requests that affect the same target as the skip_line pull request are de-prioritized. All bot pull requests associated with these de-prioritized pull requests will be closed, and the new skip_line pull request will be moved to the top of the queue. No other pull requests in the queue are impacted.

Instant merge

Instant merge is a merge method that Aviator merge the pull request directly without waiting for the CI to finish. This requires elevated permissions for Aviator and can be configured using the Pilot workflow. See the Pilot documentation to learn how to configure instant merges.

FAQ

What happens if there is more than one high priority merge?

Aviator will queue new skip_line pull requests after the existing ones (but before any non-skip_line pull requests).

What happens if the skip_line label is removed?

If the pull request does not have the merge label, then the pull request will be dequeued. Otherwise, if the pull request is still queued, the behavior varies. For repositories using the sequential queue mode, the pull request is moved back to the original position in the queue. For other modes, there is no change in the queue after removing the skip line label. This prevents causing additional queue resets.