Skip to content
This repository has been archived by the owner on Jun 22, 2022. It is now read-only.

No-op merge causes failure #4

Closed
BhaaLseN opened this issue Aug 17, 2015 · 1 comment
Closed

No-op merge causes failure #4

BhaaLseN opened this issue Aug 17, 2015 · 1 comment

Comments

@BhaaLseN
Copy link
Owner

Steps to reproduce:

  1. Create a branch to be merged
  2. Merge the branch by hand, but leave the remote branch
  3. Trigger a merge

Since the Merge has no effect, the following amend (GitRepositoryManager.cs line 133) changes the manually merged commit, and thus fails the push afterwards (even after resetting and re-pulling, since the result is the same there).

@BhaaLseN
Copy link
Owner Author

Subsequent merges also fail, since the local working copy still has the broken history...(when attempting to do the initial pull with --ff-only, since it isnt a fast-forward at this point)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant