Note that there are some explanatory texts on larger screens.

plurals
  1. POGit Syncing: Code Kicked out of One Environment; How to Investigate?
    primarykey
    data
    text
    <p><strong>I use Git</strong> to help delegate the course of a project, whose code-base is simultaneously developed by a growing team of developers. It does nearly everything we need it to do, however every so often a particular obstacle arises, whose solution escapes me: <strong>someones code gets kicked out</strong>.</p> <p>At first this question sounds fairly generic, but I'm unaware how to "categorize" this problem, and moreover I'm not sure of the most effective way to diagnose it. I can explain it, however, in a quick play-by-play.</p> <p><strong>Play-by-play</strong></p> <p><em>Setup:</em> We have three environments: A, B, and C. Each is a clone of a central repository.</p> <ul> <li>A just fixed a feature. B &amp; C still have the broken version.</li> <li>B wants A's code, to make cosmetic changes to the corrected functionality.</li> <li>C is my environment, and I perform the Git tasks.</li> <li>I merge B &amp; C first, because any conflicts will be easier resolved.</li> <li>I push this result, then pull it into A, and resolve conflicts there.</li> <li>I push this result, then pull it into B &amp; C.</li> </ul> <p>Suddenly, A's solution is gone. The feature is, again, broken everywhere. I get the impression that A's new, corrected code was mistakenly replaced.</p> <p><strong>Question #1: Is order the problem?</strong></p> <p>I'm under the impression that the order in which different clones push and pull shouldn't change the result. Am I correct? Or is my problem to do with the order of the pushes and the pulls?</p> <p><strong>Question #2: What tools are useful for diagnosing this issue?</strong></p> <p>Even after using <em>git diff</em> and GUI log tree-views, like in <em>gitk</em> or <em>TortoiseGit</em>, the solution is sometimes still unclear. Are there any other tools in the Git suite, or otherwise, which indicate how code moved, or how preference is determined?</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.
    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