> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/mergequeue/how-to-guides/how-to-block-pull-request-mergeing-with-slash-commands.md). # How to Block Pull Request Mergeing with Slash Commands Aviator supports conditionally blocking a pull request from being automatically merged in the queue using the `\aviator block until` command. When the pull request reaches the top of the queue, its specified "block until" condition is evaluated. If the condition is met, the PR is merged immediately. If not, the PR is marked as pending. Aviator then continuously checks pending PRs every minute and merges them as soon as their conditions are satisfied. ## Block Until PR `\aviator block until ` will block a pull request from being merged until the reference PR has been merged.
## Block Until Timestamp \aviator block until \ will block a pull request from being merged until the given time has passed. Examples of valid timestamps include: * Absolute ISO timestamp: `2025-02-15T12:30:00.000+0000` * Date: `2025-02-15` * Time: `9pm` * Day of the Week: `Monday` * Day + Time: `Monday 9pm`
## Cancel Block `\aviator block cancel` will cancel all block conditions placed on the PR --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.aviator.co/mergequeue/how-to-guides/how-to-block-pull-request-mergeing-with-slash-commands.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.