rich1.0npub19r53ufymeycp9wzk3yzru55y5u46e4vva2lj7nak4zrn6yhrna7qsyj32shttps://nostr.ae/npub19r53ufymeycp9wzk3yzru55y5u46e4vva2lj7nak4zrn6yhrna7qsyj32snjumphttps://nostr.ae📅 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