Jump to content
Sign in to follow this  
Stephen Taylor

name_conflict files added during merge

Recommended Posts

On merging from our main branch into a user branch the changelist lists some files with name_conflict in the file name.

I've used 'Browse repository in this changeset' to look at the contents of the user branch before merging from main and the files in question don't already exist.

I also look at the changeset in main and they are named correctly.

After the merge and submit to the user branch the files have been changed to have name_conflict in them and the originals are no longer present.

The name_conflict files are listed under Added (files added in the merge source)

My question is how is this possible?

I tried creating another changeset from our user branch before the merge was done and re did the merge to try and reproduce this issue. This time it was all fine, so I'm not sure what went wrong the first time?

I have explored a few possibly explanations.

1. What happens if the file was already submitted to the other branch (which it wasn't). In this case I get an evil twin conflict.

2. What happens if the files that I would be getting in the merge were already on my machine but not submitted? I tried this with a txt file and I didn't get any warning conflict or renaming to name_conflict. What did happen though was the file I had locally disappeared in the merge and the contents were lost. When I submitted the merge the file contained what ever was coming down from main. There was .txt.private.0 file left on my machine though which contained the local txt I would have wanted to merge. So this also went wrong but in a different way.



Share this post

Link to post
Share on other sites


This "name_conflict" files appear when a merge operation needs to download a specific file but it already exists in your workspace. It could happen for instance if you already had a private file with the same name on this path. 

Do you have "cloaked.conf" rules? There are also some scenarios it could also happen with cloaked files.




Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this