Rebase files when you need to make sure you have the most recent copy of the files including changes made by other users. See Rebasing branches.
Rebasing only applies new changes to branches. It does not copy file contents from branch to branch. An internal flag tracks the file version that was last rebased from. If a file version in the parent branch is flagged because it was already rebased to the child branch, the file cannot be rebased until the files version changes in the branch it was rebased from. It does not matter if the file contents are different. See No Files to Rebase in Surround SCM for information.
1. Select the files you want to rebase and choose Branch > Rebase Files.
The Rebase Files dialog box opens.
2. Enter any Comments, such as the reason for rebasing the files.
3. Select a Rebase files based on option.
4. Select Skip server auto-merge to rebase all changes and overwrite any changes in the child branch.
5. Select Recursive to rebase the file to the selected repository and all subrepositories.
6. Click Preview.
The Rebase Preview dialog box opens. Files that will be rebased, files that will not be rebased, and files with conflicts are displayed. You can resolve conflicts based on the file status and your security permissions. See Rebase preview.
7. Select a file and click Rebase File to rebase it or click Rebase All to rebase all files.
The Rebase Status dialog box opens. You can perform many of the same actions available in the Rebase Preview dialog box.