Matt Glaman on Nostr: npub1cu5wu…53mwq !! I need to look at this. Drupal has a standard todo comment ...
npub1cu5wu88x8r97m8hpxu88rnd8wmskrjeaxelmvgew84suwqtdz3ssr53mwq (npub1cu5…3mwq) !! I need to look at this. Drupal has a standard todo comment structure when something needs to be revisited after an issue is closed!
However, doesn't this break HEAD since it's reactive?
🤔 Our issue forks and MR flow for GitLab automatically has branch names reflect issue numbers. I wonder if something similar could read from that pattern (via config?) and flag ahead of time.
Published at
2023-12-27 18:37:01Event JSON
{
"id": "bdffc4c9174c1da047c49bd1e8079544c047a841abd4bbc121b185f230f6a6bc",
"pubkey": "f453b8d65cd29eeb0979156a57b3e916a8d34a1265f87e22f64dd54f3c765790",
"created_at": 1703702221,
"kind": 1,
"tags": [
[
"p",
"c728ee1ce638cbed9ee1370e71cda776e161cb3d367fb6232e3d61c7016d1461",
"wss://relay.mostr.pub"
],
[
"p",
"a06a5af5d27cf266cb042d0a3fdc2a3930d462184f74d35b1d094a2a8adc25fc",
"wss://relay.mostr.pub"
],
[
"e",
"df10c6583c448ad39d33767bd2ab76d033eb0fdf8ba34894b485ef2535df2f74",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://phpc.social/users/mglaman/statuses/111653828777176483",
"activitypub"
]
],
"content": "nostr:npub1cu5wu88x8r97m8hpxu88rnd8wmskrjeaxelmvgew84suwqtdz3ssr53mwq !! I need to look at this. Drupal has a standard todo comment structure when something needs to be revisited after an issue is closed!\n\nHowever, doesn't this break HEAD since it's reactive? \n\n🤔 Our issue forks and MR flow for GitLab automatically has branch names reflect issue numbers. I wonder if something similar could read from that pattern (via config?) and flag ahead of time.",
"sig": "f5632996dbeff2199d574c3f3f5a54faa07c02d526a0c01349aa579ef06c2119c9d2312dfc829fe64c325d34af92c880576ebeec010ead326eb33c5f2c3cd1e0"
}
