📅 Original date posted:2014-10-15
📝 Original message:> 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
Wladimir [ARCHIVE] /
npub1xq…ymc2p
2023-06-07 15:26:29
in reply to nevent1q…c8eh
Author Public Key
npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2pPublished at
2023-06-07 15:26:29Event JSON
{
"id": "21d7d04b7f78870b5d3c5aabb18357de103b7df2d5f900bc7208b0340e63d562",
"pubkey": "30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722",
"created_at": 1686151589,
"kind": 1,
"tags": [
[
"e",
"8e8ffc86b671332d74dc30a93d73d86bf0648414fedbd225ac787a9a2713f3b5",
"",
"root"
],
[
"e",
"f6f7019d19a7eed9ddc6f6ad884b30007c52e7dac509dca5b0e46d1ad9a77fb1",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "📅 Original date posted:2014-10-15\n📝 Original message:\u003e This all makes a lot of sense to me, and would help a lot with the\n\u003e workflow. Unfortunately github pulls and issues really have nothing\n\u003e to faciltate a multistage workflow... e.g. where something can go\n\u003e through several steps.\n\nIndeed, pull requests don't have a \"status\".\nIt would be possible to (ab)use labels for this.\n\nThe drawback of labels is that only the repository team can set these,\nthere is no way to delegate. But I suppose it'd be possible to build\nsomething on top of the github API that handles this.\n\n\u003e We're also having problems with people failing to comment on things,\n\u003e not even \"I looked at this and have no opinion\", which is really\n\u003e obstructing things.\n\nWell - the only way to avoid that is to set a reasonable deadline,\nafter which there is a default decision. You'd hope this would\nmotivate people to get involved in time.\n\nWladimir",
"sig": "3c6063ea91cb48e1691cfc706c62961e26d24ba387f4642260366e154c08d3627337ae073c56cf9a5c568986d235f54e97bdc530c66f424a4fc55f2d444a816f"
}