Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable showing issues "blocking" labels #9

Open
str4d opened this issue Mar 10, 2022 · 1 comment
Open

Enable showing issues "blocking" labels #9

str4d opened this issue Mar 10, 2022 · 1 comment

Comments

@str4d
Copy link
Collaborator

str4d commented Mar 10, 2022

Currently, the only issues (and PRs) that show up in the DAG are ones that have blocking/blocked-by edges in ZenHub. We do see standalone floating issues in the DAG, but that's an artifact of graph pruning: all of their inbound edges are to closed or merged issues/PRs, and they have no outbound edges.

It would be useful to also show some truly-standalone issues, but we don't want to show all of them (there are currently 949 open zcash/zcash issues as of writing). Instead, let's add the ability to show issues tagged with particular labels, and have those show as "blocking" the label (so we'd see a bunch of issues pointing to a synthetic node representing the label). That will enable those issues to be exposed in the DAG, and then linked into other parts of the DAG as appropriate (if we discover such links).

@str4d
Copy link
Collaborator Author

str4d commented Nov 7, 2024

In practice, we've created "label-like" issues for this kind of purpose, and it has caused problems with the sizes of the render. So instead I propose that we allow specifying labels to include issues in the DAG, but that they show up like milestones (a box).

  • If an issue has both a label and is in a milestone, it shows up in the milestone box if those are being rendered.
  • The set of configured labels forms a priority list. If an issue has more than one label, it shows up in the box of the earliest specified label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant