You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently using GitHub milestones to show everything blocking a release, but given that we have release-specific issues in the DAG, it would be much more usable to just tag those release issues with a label, and then have all upstream blockers be shown automatically in the boxes.
For sequences of labelled issues, upstream issues that are already in an earlier subgraph should be left out of later subgraphs for simplicity (i.e. the subgraphs are adjacent rather than nested).
The text was updated successfully, but these errors were encountered:
We are currently using GitHub milestones to show everything blocking a release, but given that we have release-specific issues in the DAG, it would be much more usable to just tag those release issues with a label, and then have all upstream blockers be shown automatically in the boxes.
For sequences of labelled issues, upstream issues that are already in an earlier subgraph should be left out of later subgraphs for simplicity (i.e. the subgraphs are adjacent rather than nested).
The text was updated successfully, but these errors were encountered: