--- title: Rebase description: Rebase the pull request on top of its base branch. --- The `rebase` action makes Mergify rebase the pull request on top of its base branch. This is useful when you want to ensure that your pull request is always up-to-date with the latest changes from the base branch. :::note You do not need to use this action if you use the [merge queue](/merge-queue). The merge queue automatically update the pull requests it processes as necessary, making sure they are tested with up-to-date code before being merged. ::: :::caution The `rebase` action with `bot_account` will no longer support fork pull requests after **July 1, 2026**. If you use this configuration on repositories that receive PRs from forks, switch to the [`update` action](/workflow/actions/update) instead. ::: ## Parameters | Key name | Value type | Default | Description | | --- | --- | --- | --- | | `bot_account` | template or null | `null` | To rebase, Mergify needs to impersonate a GitHub user. You can specify the account to use with this option. If no `bot_account` is set, Mergify picks the pull request author. The user account must have already been logged in Mergify dashboard once. **Warning:** Due to security on GitHub side, rebase cannot be performed on pull requests created by bot accounts without explicitly setting the `bot_account` impersonation option. | ## Examples