3
For feature branch, you will usually need two merge operations.
First, you will periodically take changes from trunk. Second, after the feature is verified and ready for use, you will need to
deliver changes to trunk.
To take changes from trunk,
- Go to new Subversion Working Copies information in Changes toolwindow
- Click Merge from
- Select trunk in branch selector popup
In case your working copy format does not support svn:mergeinfo (earlier that 1.5), merge from trunk will start
immediately (svn merge <trunk-url> <working-copy-path>)
If your working copy format is 1.5 or newer, and merge information can be gathered, you will be prompted:
In case you want to check everything thoroughly, a dialog with not merged revisions is shown, where you can
browse changes and/or exclude some of them from merge: (see Merge information gathering rules)
1|Page
If you have any local changes that can accidentally intersect merged changes, you will be prompted about that
with following options:
Local changes can be automatically shelved, you can ignore warning, or choose to inspect local changes before
the merge.
Intersecting changes will be shown in Version Control toolwindow if you have selected inspect changes (only
for the case when youre merging a fixed subset of revisions.)
If merge is successful, commit dialog is shown with preset commit message containing information about merge
source, and preselected merged changes
2|Page
All merged changes are put into a new separate changelist, so you will be able to deal with conflicts or commit
changes later
To merge branch changes back into trunk, you should open trunk working copy and do same steps as when taking
changes from trunk into branch (selecting source branch in popup). Additionally, you will be warned:
4|Page