Help Center
Note: Zenhub's full feature set is unlocked when you connect your GitHub Organization to Zenhub

Merge multiple GitHub repositories to make multi-repo Workspaces

Software projects often span across several GitHub repositories, so naturally, your Workspace tracker and reports should too.


Using Zenhub, you can connect repositories together—even across GitHub organizations—to get a bird's eye view into everything going on with your software projects. 


Creating multi-repo Workspaces

To merge multiple repositories together, get started using the Repos dropdown on the top left of any Zenhub Board.


To merge repositories together, you need to have write permissions to all repositories in GitHub you'd like to merge.


Using the Add repos option, search for the repository that you'd like to connect. Using the avatar on the bottom left of the modal, you can toggle across all organizations and personal repositories that you have access to. If the repository you'd like to add is in another one of your GitHub organizations, you can connect this using the custom link on the bottom left, where the avatar for your organization is located. 


After confirming the repository you'd like to connect to your Workspace, you'll be brought to your Board where all issues from this repository will be placed in the first New Issues pipeline. Note: For ZenHub On-Premises customers please follow our guide on issue placement when adding repos to a Workspace


For Zenhub Cloud customers, to sort Issues into various pipelines we'd recommend:

  • Leveraging filters and multi-action to bulk move issues into their appropriate pipelines.
  • If you'd like to copy the pipeline groupings from another Workspace for this repo, leverage automated Workflows to automate the movement of issues into different pipelines. Learn more about getting started with Automated Workflows here

Important! Before merging Boards together, have a discussion with your team.

 While you can disconnect a repository from the central multi-repo Workspace at any time, the prioritization of all Issues inside the Board will be lost once disconnected. Make sure your team is onboard with the merge beforehand.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.