<oembed><type>rich</type><version>1.0</version><author_name>npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p</author_name><author_url>https://nostr.ae/npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-10-15&#xA;📝 Original message:&gt; This all makes a lot of sense to me, and would help a lot with the&#xA;&gt; workflow.  Unfortunately github pulls and issues really have nothing&#xA;&gt; to faciltate a multistage workflow... e.g. where something can go&#xA;&gt; through several steps.&#xA;&#xA;Indeed, pull requests don&#39;t have a &#34;status&#34;.&#xA;It would be possible to (ab)use labels for this.&#xA;&#xA;The drawback of labels is that only the repository team can set these,&#xA;there is no way to delegate. But I suppose it&#39;d be possible to build&#xA;something on top of the github API that handles this.&#xA;&#xA;&gt; We&#39;re also having problems with people failing to comment on things,&#xA;&gt; not even &#34;I looked at this and have no opinion&#34;, which is really&#xA;&gt; obstructing things.&#xA;&#xA;Well - the only way to avoid that is to set a reasonable deadline,&#xA;after which there is a default decision. You&#39;d hope this would&#xA;motivate people to get involved in time.&#xA;&#xA;Wladimir</html></oembed>