GitHub Projects: Manage repo-specific issues seamlessly
Published: 2024-03-28 04:10:25

The speaker presents a thoughtful exploration of project management on GitHub, emphasizing the evolution of strategies to suit team size and efficiency. Initially, the speaker discusses the challenge of managing multiple projects per repository, leading to a revised approach of consolidating tasks within fewer projects. They highlight the benefits of this streamlined method, particularly for small teams, while also acknowledging alternative options like maintaining a single project across all repositories. Ultimately, the optimal solution emerges as maintaining separate projects in GitHub repositories while utilizing a master project on Snowpal for a cohesive overview. This approach offers a balance between organization and accessibility, providing a federated view of all related work across repositories, ensuring effective project management.

### Summary

**Introduction to GitHub Project Management:**
- Overview of managing projects or repositories on GitHub.
- Mention of using GitHub primarily for managing projects.

**Initial Project Management Approach:**
- Description of initially creating multiple projects in each repository to manage different tasks.
- Challenges faced with this approach, especially for small teams.

**Revised Project Management Strategy:**
- Transition to having fewer projects, primarily one per repository for current activities.
- Explaining the structure of having a project with multiple columns for different tasks within a repository.

**Alternative Project Management Options:**
- Mention of maintaining all tasks in one project across multiple repositories.
- Discussion on the drawbacks of this approach.

**Optimal Project Management Solution:**
- Description of having separate projects in GitHub repositories to manage and maintain them efficiently.
- Introduction of a master project on SnowPal Pitch to oversee all repositories and projects collectively.

**Conclusion:**
- Recap of the preferred approach for managing projects on GitHub.
- Mention of a master project for a federated view of all related work.

### Podcast

Check out on [Spotify](https://open.spotify.com/episode/4myGfRsgApgzfd6GA6mhPg?go=1&sp_cid=c13c6333498d3c94fe4c91c5ca3c53bc&utm_source=embed_player_p&utm_medium=desktop).

### Transcript

**0:01**  

Hey there, in this video let’s quickly talk about managing your projects or repos on GitHub. We manage our projects obviously on [snowpal.com](https://snowpal.com/), but in addition to that, you know from a repo management standpoint, we have several repositories like the UI, API, mobile and scaffolds, and a number of repos that our application, our platform comprises of and we use GitHub to manage these projects, right.

**0:28**  

We use GitHub primarily to manage these projects and I kind of like Github's UI and it does a ton of stuff. But The thing is you have to figure out what works for your team. So I had initially created a single project, no actually multiple projects in each of those repos to manage the different items that we need done or we plan to get done.

**0:48**  

So for each vertical service, or for a horizontal feature, a platform feature that we're gonna implement, how to create a project in each of the repos that have had its dependencies. So that would be a UI project, a repo and a UI project in a UI repo, a project in API repo and mobile repo and so on and so forth.

**1:09**  

Which works fine in terms of you want to keep them separated, but it's it's difficult to maintain if you're a small team. So then I switched. I changed gears to actually having only a couple of projects and primarily one per repo for the current set of activities.

**1:26**  

So you would go to the UI repo and actually have a project, a bunch of issues. And for the vertical services and the horizontal platform features, I just created a column in that particular project and all of the issues associated in that repo. This way at least you don't have to go to N different places.

**1:43**  

One other option is to just maintain it in one project, keep one project and deal with all of your repos. But that's not, I mean that has a lot of other issues. So what we the option, the approach that works very well for us is you have different projects in these GitHub repos to manage and maintain those particular those repositories specifically.

**2:05**  

And then we have a master project on snow pal pitch to manage all of these repos collectively, right. So let's say like I mentioned a number of repos and a number of projects, at least two projects per repo. But there would be a master project using a platform project key that you can create on snowpal that points to all of these repos and projects.

**2:25**  

That way it gives you a current or a Federated view of everything else that's happening that's related to the work that you're performing. So just my two cents. Thanks.