You can also see the new branch in TortoiseSVN’s Revision Graph. The current branch in the working copy can be verified using the svn info cli command. I selected Switch working copy to new branch/tag in the Copy dialogue when I created the branch.
In this case, close the warning and select Create copy in the repository from: Working copy. In this case, you will likely want your edits (and any new files) to become the first commit in the new branch. If you are creating the branch in hindsight and have already made file edits, TortoiseSVN will warn you that basing the branch on HEAD will result in loss of those edits. If there are no edited files in the working copy, the Copy dialog will default to using the most recent version as the base for the branch. You can select HEAD or a specific version to base the branch on. Select the path for the branch, a log message, and the base for the branch. Right-click on the local repository workspace folder in Windows Explorer and pick TortoiseSVN -> Branch/tag… from the Context menu. I’m following Subversion best practices for my project directory structure, using trunk, tags and branches sub-directories.
SUBVERSION CREATE TAG DRIVER
Working on the msp432logger project, I wanted to refactor the code to create a distinct logging application, separate from the driver level, and created a new branch for the work called TRY-loggerapp. The new development may be used, for example, to code a new feature, to perform release stabilization, or to experiment with refactoring, and will be merged back into the main branch when the work is complete.
It is generally considered good practise with Subversion to keep trunk for stable useable code, and create a development branch from trunk for new development.