# Backporting In many development workflows,developers may create separate stable branches for release candidates that are different from the trunk or default branch. In such cases, the branches may diverge significantly if they are long lived. For instance, if there is a release candidate branch called release-v3.4 where a bug was found, the developer may prepare a bug fix for this release branch, but now this bug fix should be made in the other branches as well. This can be easily done using backporting. You can tell Aviator to backport a particular PR on another base branch. Aviator will create a new PR that cherry picks the changes from the original PR and applies on the specified base branch. --- # Agent Instructions: 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: ``` GET https://docs.aviator.co/mergequeue/concepts/backporting.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.