In the Working Copy view or
in the Repositories view,
select the resource which you want to copy to a branch or tag, then select the command
Branch / Tag... from the Tools menu.
The Branch / Tag dialog
The default target URL for the new branch / tag will be the repository URL of the selected
resource from your working copy, divided in two: the URL of the parent and the selected
resource's name. You may specify other resource name if you want to make a branch / tag using
a different name than the one of the selected resource, by modifying the field labeled
Under the name:. The new branch / tag will be created as child of the
specified repository directory URL and having the new provided name. To change the parent
directory URL to the new path for your branch / tag, click on the
Browse button and choose a repository target directory for your
resource.
You can also specify the source of the copy. There are three options:
- HEAD revision in the repository - The new branch / tag will be
copied in the repository from the HEAD revision. The branch will be created very quickly
as the repository will make a cheap copy.
- Specific revision in the repository - The new branch will be
copied in the repository but you can specify exactly the desired revision. This is useful
for example if you forgot to make a branch / tag when you released your application. If
you click on the History button on the right you can select the
revision number from the
History dialog. This type of branch will also be created
very quickly.
- Working copy - The new branch will be a copy of your local
working copy. If you have updated some files to an older revision in your working copy, or
if you have made local changes, that is exactly what goes into the copy. This involves
transferring some data from your working copy back to the repository, more exactly the
locally modified files.
When you are ready to create the new branch / tag, write a commit comment in the
corresponding field and press the
OK button.