ploum on Nostr: Reading npub1sg4rc…7xslc , I became convinced that the Github workflow was ...
Published at
2023-12-06 16:33:08Event JSON
{
"id": "bbd0447f847e2f923cb9e6bfcbbd5011fc1be3c618ad2a4bea9623377692497e",
"pubkey": "82c970c09c842122936d413b803c357e5648eae588d7ad4b623cb6b2ebdccf32",
"created_at": 1701880388,
"kind": 1,
"tags": [
[
"p",
"822a3c32c6b06303792fc98e35b5a527f0d6a938bad3b52924ad2f573d418bf4",
"wss://relay.mostr.pub"
],
[
"p",
"05bbadaea41d30c3cf3b7fb1027622eb00cca66635fc9047053df7f9a54cb0c7",
"wss://relay.mostr.pub"
],
[
"proxy",
"https://mamot.fr/users/ploum/statuses/111534433160261514",
"activitypub"
]
],
"content": "Reading nostr:npub1sg4rcvkxkp3sx7f0ex8rtdd9ylcdd2fchtfm22fy45h4w02p306qq7xslc , I became convinced that the Github workflow was suboptimal (something I had the intuition). \n\nAs a free software maintainer, I can’t tell how much my life is simpler with sourcehut, reviewing patches through email and applying them without having to merge PR.\n\nBut what was the traditionnal old-school approach seems to become trendy again under a new name: \"stacking\"\n\nhttps://graphite.dev/blog/your-github-pr-workflow-is-slow\n\nPeople keep reinventing the wheel and giving it new names. That’s how it works…",
"sig": "259b6661e2f5f32ede169fcdf8f5c135d24c22d6abd6872c751fc611aa9e9ba4bf3c5d5ad295d517d897e352c27d9fc2fe70aef5215ca962a8e4957f703015ae"
}