Re:Can we communally deprecate git checkout?
by JohnMakin on Thursday January 09, 2025 @07:54PM
(#42651415)
I think this nails the difference in my workflow against people that tend to say it is difficult. In infrastructure commit history, which is often tied to CI CD processes that reach far outside of a repository and org - commit history is sacred. I need the absolute order of when things got merged in, because it provides a clean timeline to backtrack any issues. maybe I’m doing it wrong but every mature sysyem I’ve worked in basically operates this way. I suspect you run into more merge conflicts but I’m by no means a git expert.
[ Parent
| on HN ]
Re:Can we communally deprecate git checkout?
by AlotOfReading on Thursday January 09, 2025 @08:58PM
(#42651739)
The best I've found is the kernel development process: use both intelligently and give your branches a clean commit history before they're sent for review.
https://docs.kernel.org/maintainer/rebasing-and-merging.html