What happens to uncommitted changes in the destination branch during back promotion?

During back promotion, uncommitted changes in the destination branch will be overridden. This process involves promoting changes from one environment to another, typically going back to a previous environment or branch to ensure that the most relevant code is deployed.

When back promotion occurs, any uncommitted changes that are present in the destination branch are essentially replaced by the incoming changes being promoted. This means that unless those uncommitted changes were explicitly committed prior to the back promotion, they will not survive this operation.

This action ensures a clean and consistent code base is maintained, allowing for the integration of changes without the risk of potential conflicts that could arise from having uncommitted work in the branch. Understanding this can help in managing your workflow effectively and ensuring that necessary changes are captured before they are overridden.