Event JSON
{
"id": "4a2e35d3275611e324fd95df4b5871def554f66a4bf96dac63ff9637c5062992",
"pubkey": "7ef1d6c60aaab55c2d628312aa92218dfd94222749009257d30023ce6beef717",
"created_at": 1710748008,
"kind": 1,
"tags": [
[
"p",
"ec6e9c3011774a24221c1fa3e1964f2d2d7f68602574ecd0f217235a1bf59c72",
"wss://relay.mostr.pub"
],
[
"p",
"579852afc54f2f4b992d5c48441d63f6545c530a7371764b6e67325d585ea6a1",
"wss://relay.mostr.pub"
],
[
"t",
"sourcehut"
],
[
"proxy",
"https://mastodon.social/users/quaff/statuses/112115581456516465",
"activitypub"
]
],
"content": "Been evaluating #sourcehut, and noticed that the service uses git send-email rather than pull requests like other git services. I’m reading why this article by nostr:npub1a3hfcvq3wa9zggsur737r9j095kh76rqy46we58jzu345xl4n3eqz9m44m \n\nhttps://blog.brixit.nl/git-email-flow-versus-github-flow/\n\nI’m seeing talk of force-pushing after opening a PR. Why force-push after a PR is opened? Are y’all trying to undo/edit commits? Cause that seems like just bad practice to me. If so, why aren’t you just squash merging? Maybe I’m missing something here.",
"sig": "66103a56c5f6c2350fc0747917e77ecd5f87620ddabc5513b21f3c25d87d5284d33ba7e9242f3924bc400768fce145313340efaba76ba62345229d31b0dec802"
}