Repository Groups

Repository Groups let you organize your repositories into logical collections for easier filtering and analysis. This is especially useful for larger organizations where different teams own different sets of repositories.

Use Cases

• Team-based views: "Backend Team", "Frontend Team", "Platform"
• Project-based views: "Payments System", "User Service", "Admin Tools"
• Environment-based views: "Production Services", "Internal Tools"

Creating a Group

1. Go to the Overview dashboard
2. Use the filter dropdown to select the repositories you want in the group
3. Click Save selection as group...
4. Enter a name for the group
5. Click Save

Using Groups

Quick Selection

Once created, groups appear in the filter dropdown under "Saved Groups". Click a group to instantly filter the dashboard to those repositories.

URL Sharing

When you select a group, the URL updates to include ?group=<id>. Share this URL with teammates to give them the same filtered view.

Dashboard Subtitle

The dashboard subtitle updates to show the active group name, so you always know what you're looking at.

Managing Groups

Editing a Group

Currently, to edit a group you need to:

1. Delete the existing group
2. Create a new group with the updated repositories

A direct edit feature is coming soon.

Deleting a Group

1. Open the filter dropdown
2. Hover over the group you want to delete
3. Click the trash icon
4. Confirm deletion

Deleting a group does not affect the underlying repositories or their data.

Pinned Repositories

In addition to groups, you can pin individual repositories:

1. Go to the repository detail page
2. Click the Pin button

Pinned repositories:

• Appear at the top of repository lists
• Can be quickly selected via the "Pinned" quick filter
• Are user-specific (not shared with team)

Best Practices

Keep Groups Focused

Create groups with 5-15 repositories that genuinely belong together. Very large groups defeat the purpose of filtering.

Use Descriptive Names

"Backend" is better than "Group 1". "Payments Team" is better than "PT".

Combine with Pinning

Pin your most-used repositories, create groups for team views. Use both together for maximum efficiency.