3 ms·
if the workflow magically avoids conflicts, why not give them 2 commands to update/commit&push and keep all the power of git to who need it? also, you do know
by gcb0 10y ago
if the workflow magically avoids conflicts, why not give them 2 commands to update/commit&push and keep all the power of git to who need it?
also, you do know that conflicts are going to show up eventually right?
- bachmeier 10y ago> if the workflow magically avoids conflicts, why not give them 2 commands to update/commit&push The workflow doesn't avoid conflicts. > keep all the power of git to who need it Git provides no useful features over Fossil for what we're doing. > you do know that conflicts are going to show up eventually right And when they show up with Git, boy do they show up.