Waiting for the day when some adds AI to git's merge algorithms to avoid conflicts while cherry-picking, rebasing, merging.
Well. Do I? Not really.
Waiting for the day when some adds AI to git's merge algorithms to avoid conflicts while cherry-picking, rebasing, merging.
Well. Do I? Not really.
"'It was fine before we added your code' doesn't mean that the team merged last did a poor job. This is counterintuitive but worth considering. If the merges had happened in the opposite order, the other team would seem to be at fault."
#softwareengineering #developerexperience #mergeconflicts #continuousintegration
Do you experience missed release schedules, flawed releases that must be rolled back, and error reports from customers?
These are common problems arising from the same underlying cause (at scale).
#Nix support is now ready and has been included in the brand new
🔀🦒 #Mergiraf v0.6.0 release!
https://codeberg.org/mergiraf/mergiraf/releases/tag/v0.6.0
(Mergiraf is a syntax-aware #git #merge driver that solves many conflicts automatically that git's built-in merge strategies can't.)
#opensource #coding #programming #cvs #mergeconflicts #git #gitmerge
### New languages * SystemVerilog (*.sv, *.svh), by @come_744 (#226) * Nix (*.nix), by @funkeleinhorn (#183) ### New features * feat(LangProfile::detect_from_filename): handle extension comparison more correctly, by @ada4a (#220) * feat(`MergedTree::line_based_local_fallback_for_revnode`)...