Show when something is depending on other people

[victorb]

Random idea: Show when people are dependents for finishing something. You could have something like this in a issue:

depends on @VictorBjelkholm

and that would show up as a similar card but slightly different. Also should be possible to search by user so I can see what's depending on me.

[jbenet]

why not get this via assignee in an issue? ideally we would use issues (not people) as dependents

[wking]

On Wed, Feb 15, 2017 at 06:27:34PM -0800, Juan Benet wrote:

why not get this via assignee in an issue? ideally we would use issues (not people) as dependents

I agree with this, and 1 (which only gets the first 100 issues) is an already-working part of this (a user's issues, but not limited by repo). If we have thoughts on a URL scheme for a graph containing only (or just rooted in?) issues assigned to a user in a given repo, that would be fairly straightforward to implement (pass options to listIssues 2). So:

• What is the URL for this? /{owner}/{repo}/{user}? /{owner}/{repo}?person={user}?

• What happens if an issue assigned to that user depends on an (open?) issue assigned to someone else? Assigned outside that repository? Our current approach with this sort of thing is to keep walking the graph as long as we find open dependencies (regardless of whether they match the initial query), but #13 and #17 are floating other (optional?) approaches.