Can Lists be Used at the Team Level?

[ShelliOrton-Rogers]

We are migrating from Bitbucket to Github. Bitbucket groups related repos into projects but they are not the same as Github projects. I found this SO post from someone else also migrating and looking for how to group repos: https://stackoverflow.com/questions/61466956/can-we-have-multiple-repositories-inside-a-project-in-github

In that post it was recommended to use Github lists to achieve the same organization/grouping. Reading this page, I'm under the impression that lists belong to an individual: https://docs.github.com/en/get-started/exploring-projects-on-github/saving-repositories-with-stars

Is that correct? Is there a way to use lists across mulitple users/Github team?

[Anghel01]

You're correct — Lists in GitHub are personal and tied to individual accounts, so they can't be shared across a team.
For team-level grouping of repositories, the best options are:

GitHub Topics — add the same topic tag to all related repos. Anyone in the org can search/filter by topic. It's not a folder but works well for grouping.
GitHub Organizations + Teams — you can create Teams within your org and give them access to specific sets of repos, which effectively groups them by team ownership.
GitHub Projects — you can add multiple repos to a single Project board at the org level, which gives you a shared view across repos.
Pinned repositories — at the org profile level you can pin up to 6 repos for visibility.

For migrating from Bitbucket Projects specifically, GitHub Organizations with Topics is probably the closest equivalent for grouping without the overhead of managing Projects boards.

[ShelliOrton-Rogers]

Thank you! Looks like we need to use topics.