The Case of the Moving Merge Base
hoelz.ro·3d
🕰️RetroCRDTs
Preview
Report Post

A while ago, my friend and coworker Matt pinged me with a Git question. He was looking into an issue with a GitHub Actions workflow that only runs on files that changed in a given pull request, and a user reported that it was running against way too many files - so many, in fact, that the workflow was failing because it was exceeding the maximum command line length!

Now, the set of files changed by a pull request is determined by the merge base between the commits at the tips of the source and target branches - it’s basically their most common ancestor. Matt showed me the logs from the workflow, which was logging the commit ID for the merge base - but when we ran the exact same git merge-base command locally, we got a different commit back! The only real difference between our…

Similar Posts

Loading similar posts...

Keyboard Shortcuts

Navigation
Next / previous item
j/k
Open post
oorEnter
Preview post
v
Post Actions
Love post
a
Like post
l
Dislike post
d
Undo reaction
u
Recommendations
Add interest / feed
Enter
Not interested
x
Go to
Home
gh
Interests
gi
Feeds
gf
Likes
gl
History
gy
Changelog
gc
Settings
gs
Browse
gb
Search
/
General
Show this help
?
Submit feedback
!
Close modal / unfocus
Esc

Press ? anytime to show this help