Event JSON
{
"id": "80defdd40b9dc62c361f8c8cafff5f82b2d2b7dedeb5d652b95b4e371f458a24",
"pubkey": "15509f408668c7caa08edafb9132e587f5f868506db546abc4339a3f2963756c",
"created_at": 1728587888,
"kind": 1,
"tags": [
[
"p",
"5c91d587cf41bc819852e8486c9ef59f3b46752c808790b3574c459a7429473b",
"wss://relay.mostr.pub"
],
[
"p",
"572378b71785ffa7cff103804ff3098aa3f3f9b421aedabe28820079265d4831",
"wss://relay.mostr.pub"
],
[
"e",
"64e8fed6b33ef444be2df727b676b0d0998f89bb743329915e5e2566a53ec850",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fosstodon.org/users/martinpitt/statuses/113284735828569828",
"activitypub"
]
],
"content": "nostr:npub1tjgatp70gx7grxzjapyxe8h4nua5vafvszrepv6hf3ze5apfguaspmgye3 I'm not sure that I get your point. Sure there are situations where you need to integrate stuff from several projects into one artifact or deployment. What stops you from expressing that as yml pipelines? Complexity/dependency graphs and how to manage the CI logic (yml in git or something external like Jenkins) feels mostly orthogonal to me, and IME git+yaml is vastly superior.",
"sig": "cf08c685e67fe5353819abd7e753550e6048d50934069a617d4a9fdb9f38842757fec001ac6e469f3259291472bd2ce6ea350f1510ba899718b9109b379a3313"
}
