Top all-time · #22083
MergeBase
Company blog · mergebase.com/blog · on HN as juliusmusseausecurityprogramming
MergeBase is the company blog at mergebase.com, writing about security and programming. Since 2018, 3 different Hacker News readers have linked it 6 times. The last post was in 2024, but the archive is still widely read.
Too few sampled comments (1) to say how often HN recommends it.?
Why HN links it
MergeBase is a blog on git and software development. The linked post argues that developers should not fear rewriting history and should always use git pull -r with --autosquash.
Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
MergeBase’s Software Composition Analysis Platform protects apps from attacks on known vulnerabilities with the lowest false positive rate.
What Hacker News says?
I wrote this and wish more people followed this specific git advice: https://mergebase.com/blog/doing-git-pull-wrong/ TLDR: don’t be afraid of rewriting history but ALWAYS do “git pull -r —autosquash “
Comment linking /blog/doing-git-pull-wrong/
on “Git tips and tricks”Submitted Too much fun with “git pull –rebase” as a story · 11 points
HN discussionJoking aside, "git pull -r" is pure magic in the face of upstream rewrites. It always does the right thing: https://mergebase.com/doing-git-wrong/2018/03/07/fun-with-gi... After I wrote that blog post someone told me the reason for the magic is the use of "git merge-base --fork-point" under the hood.
Comment linking /doing-git-wrong/2018/03/07/fun-with-git-pull-rebase/
on “Linus’s rules on keeping Git history clean (2009)”Submitted Ldd /usr/sbin/sshd – Alpine vs. Ubuntu for exploitability of CVE-2024-3094 as a story · 10 points
HN discussionSubmitted Industry the True Costs of False Positives in Software Security as a story · 1 points
HN discussionSubmitted Too much fun with “Git pull –rebase” as a story · 1 points
HN discussion