You can use the tree goal of the Maven dependency plugin to display all transitive dependencies in your project and look for dependencies that say “omitted for conflict”.1 mvn dependency:tree -Dverbose mvn dependency:tree -Dverbose | grep ‘omitted for conflict’ Once you know which dependency has version conflicts, you can use the includes parameter to show … Read more
If you know the ref, then git show <MERGE_COMMIT> will show you the resolution done (if any) for the merge commit. For log, use git log -p -c or git log -p –cc. From the manpage of git log: -c With this option, diff output for a merge commit shows the differences from each of … Read more
I can’t tell you what’s wrong, but you might try git reset app/models/disclosure_even.rb git add app/models/disclosure_even.rb and then commit.
The basic problem here is the use of branches (dev-master) instead of tagged versions. Using branches is very likely to end in problems. I am watching the Composer questions on Stackoverflow, and every time someone reports trouble with packages, they are using development branches and “minimum-stability:dev” 99% of the time. What’s happening? I must assume … Read more
Situation: You have local uncommitted changes You pull from the master repo You get the error “Checkout conflict with files: xy” Solution: Stage and commit (at least) the files xy Pull again If automerge is possible, everything is ok. If not, the pull merges the files and inserts the merge-conflict markers (<<<<<<, >>>>) Manually edit … Read more
I had this exact question so I found this post two years later. However, I think it is important to note that this will only not compile and give the “The call is ambiguous” error if the code calling the duplicate extension methods is not in the same namespace as one of them. If the … Read more
In the user settings, you can disable Git Merge Editor: VS Code Settings Screenshot
What you are seeing means that automatic merge could not resolve the conflicts in the files. You need to resolve these conflicts manually. Run git mergetool or git gui.
While doing a git svn rebase, if you have merge conflicts here are some things to remember: 1) If anything bad happens while performing a rebase you will end up on a (no-branch) branch. 2) If you run git status, you’ll see a .dotest file in your working directory. This is safe to ignore. 3) … Read more
Skipped obstructing working copy this means that there’s a working copy folder in the way: your update wants to add a folder with name ‘project’, but you already have a versioned folder ‘project’ in your working copy. Maybe you moved that folder from another working copy? Or that folder is its own working copy (if … Read more