Closed bernhold closed 3 years ago
Related to this, all repositories should have a common set of labels and milestones.
We now have a tool to synchronize issue labels and milestones across the repositories and an action to automatically add all issues and PRs to the org-level project board. I think this will be good enough. If not, we can open a new ticket.
We have multiple repositories that are closely inter-related. What is the best way to structure and handle issues across them? Should we just put everything into the organization-level board? Should (some) issues remain in their specific repos? In which case, do we need a separate board for each individual repository? If we're using multiple boards, what's the easiest way to ensure that issues end up on the appropriate board with a minimum of user thought or action?