📅 Original date posted:2014-10-15
📝 Original message:Sounds like this is what you're after, it's a fairly new feature:
https://github.com/blog/1375%0A-task-lists-in-gfm-issues-pulls-comments
I've been meaning to use it in a PR to try it out.
Cory
On Wed, Oct 15, 2014 at 5:36 AM, Wladimir <laanwj at gmail.com> wrote:
>> This all makes a lot of sense to me, and would help a lot with the
>> workflow. Unfortunately github pulls and issues really have nothing
>> to faciltate a multistage workflow... e.g. where something can go
>> through several steps.
>
> Indeed, pull requests don't have a "status".
> It would be possible to (ab)use labels for this.
>
> The drawback of labels is that only the repository team can set these,
> there is no way to delegate. But I suppose it'd be possible to build
> something on top of the github API that handles this.
>
>> We're also having problems with people failing to comment on things,
>> not even "I looked at this and have no opinion", which is really
>> obstructing things.
>
> Well - the only way to avoid that is to set a reasonable deadline,
> after which there is a default decision. You'd hope this would
> motivate people to get involved in time.
>
> Wladimir
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Cory Fields [ARCHIVE] /
npub19r…yj32s
2023-06-07 15:26:29
in reply to nevent1q…3k8w
Author Public Key
npub19r53ufymeycp9wzk3yzru55y5u46e4vva2lj7nak4zrn6yhrna7qsyj32sSeen on
wss://relay.nostr.bandPublished at
2023-06-07 15:26:29Event JSON
{
"id": "7eb63347bc9d7df99ab0a4e2f3a41bcf5cdaf7a493516fec6c07d31766060782",
"pubkey": "28e91e249bc93012b85689043e5284a72bacd58ceabf2f4fb6a8873d12e39f7c",
"created_at": 1686151589,
"kind": 1,
"tags": [
[
"e",
"8e8ffc86b671332d74dc30a93d73d86bf0648414fedbd225ac787a9a2713f3b5",
"",
"root"
],
[
"e",
"21d7d04b7f78870b5d3c5aabb18357de103b7df2d5f900bc7208b0340e63d562",
"",
"reply"
],
[
"p",
"30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722"
]
],
"content": "📅 Original date posted:2014-10-15\n📝 Original message:Sounds like this is what you're after, it's a fairly new feature:\nhttps://github.com/blog/1375%0A-task-lists-in-gfm-issues-pulls-comments\n\nI've been meaning to use it in a PR to try it out.\n\nCory\n\nOn Wed, Oct 15, 2014 at 5:36 AM, Wladimir \u003claanwj at gmail.com\u003e wrote:\n\u003e\u003e This all makes a lot of sense to me, and would help a lot with the\n\u003e\u003e workflow. Unfortunately github pulls and issues really have nothing\n\u003e\u003e to faciltate a multistage workflow... e.g. where something can go\n\u003e\u003e through several steps.\n\u003e\n\u003e Indeed, pull requests don't have a \"status\".\n\u003e It would be possible to (ab)use labels for this.\n\u003e\n\u003e The drawback of labels is that only the repository team can set these,\n\u003e there is no way to delegate. But I suppose it'd be possible to build\n\u003e something on top of the github API that handles this.\n\u003e\n\u003e\u003e We're also having problems with people failing to comment on things,\n\u003e\u003e not even \"I looked at this and have no opinion\", which is really\n\u003e\u003e obstructing things.\n\u003e\n\u003e Well - the only way to avoid that is to set a reasonable deadline,\n\u003e after which there is a default decision. You'd hope this would\n\u003e motivate people to get involved in time.\n\u003e\n\u003e Wladimir\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Comprehensive Server Monitoring with Site24x7.\n\u003e Monitor 10 servers for $9/Month.\n\u003e Get alerted through email, SMS, voice calls or mobile push notifications.\n\u003e Take corrective actions from your mobile device.\n\u003e http://p.sf.net/sfu/Zoho\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development",
"sig": "632c45be80bc1b399b317459072c698ec064213a575133ef6d2dd19d3595b62ef4a47fd72c9d3f3f0ddb6f105f07c22fcc607588cfa3799b040e76fa8d5c616c"
}