Julia Evans on Nostr: i think my favourite answer to “how do you make sense of git merge histories" so ...
i think my favourite answer to “how do you make sense of git merge histories" so far is “use git log --merges"
this seems pretty good, but it's hard to get a nice one-line summary of each merge with `--oneline` because the first line of the merge is just something like "Merge pull request #148 from briankassouf/race-detector” (instead of “Add a -race flag to enable Go's race detector on builds" which would be a more useful summary)
(2/?)
Published at
2023-12-15 17:17:35Event JSON
{
"id": "a5912486f4bf1c18b05f6604a21e797fdf1564de25d80f3c0641abb0215e3f6c",
"pubkey": "26cad6f140bf86de9c26b7c15419cab1aebdd7086358d26aa2d750e21cf3bf2e",
"created_at": 1702660655,
"kind": 1,
"tags": [
[
"e",
"fb29763fb359219d5f7e01ec0a1d9d9a5c2afe43b94fcd7ac024bcd2bb4c688d",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.jvns.ca/users/b0rk/statuses/111585568750394047",
"activitypub"
]
],
"content": "i think my favourite answer to “how do you make sense of git merge histories\" so far is “use git log --merges\"\n\nthis seems pretty good, but it's hard to get a nice one-line summary of each merge with `--oneline` because the first line of the merge is just something like \"Merge pull request #148 from briankassouf/race-detector” (instead of “Add a -race flag to enable Go's race detector on builds\" which would be a more useful summary)\n\n(2/?)\n\nhttps://cdn.masto.host/socialjvnsca/media_attachments/files/111/585/568/458/208/558/original/b3b2895e53c08aa1.png",
"sig": "45a3498739727cd4f376a9e7f4bbb71ffac265a0592d99eea49c8d1704e29f8c59daf4ba70a4a4a83d505617e4ada3bda8d895a5aa1f3df77acc4595d2246177"
}