Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy would a user's changes be overwritten without mention of a conflict?
    primarykey
    data
    text
    <p>I am working on a two person team. I made some changes to a file called PostSet. I pushed those changes. My partner had also made changes to the same file, and even to the same query. He ran </p> <pre><code>git pull --rebase origin master </code></pre> <p>in order to put his changes on top of mine and keep the working history clean, as we always do. Normally we get conflicts if we edit the same line. </p> <p>He was notified of a whole bunch of conflicts relating to some image files (a completely different issue). Just to explain everything, he fixed that problem by using</p> <pre><code>git rm -r path/to/image/dir </code></pre> <p>and then</p> <pre><code>git add -A </code></pre> <p>to add all of those changes to the index. After using</p> <pre><code>git rebase --continue </code></pre> <p>there were no more conflicts. We immediately noticed, however, that the relevant query was now using MY changes, not his. In fact, the entire file PostSet was on an old version after the rebase.</p> <p>Shouldn't there have been some sort of conflict warning about the PostSet file? Is there something we did wrong with the rebase?</p> <p>In short, we can't confidently continue development until we know changes will stop being overridden, so we're fairly frustrated.</p> <p>Thanks a lot,</p> <p>Paragon</p> <p>Edit: We replicated our steps exactly and got the same result.</p> <p>Edit: Given that nobody seems to have any clue, I will likely be reporting this as a bug in git. I'll leave it up for a while longer on the off chance that someone has a wild suggestion.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload