As part of our ongoing commitment to accelerate human progress through Social Impact initiatives, we’re offering students 30-minute, 1:1 micro-mentoring sessions with GitHub employees ahead of Universe.
Organizing your projects and teams efficiently on GitHub can provide clear direction for your teammates—and transparent documentation for everyone else following along.
In our latest webcast, GitHub Solutions Engineer Phil Holleran shares a few strategies to help you stay organized. If you weren’t able to join us live, you can find the full recording, along with a few highlights, below.
There are plenty of ways to organize teams within your company and on GitHub. Choosing the right organizational structure is key to communicating across teams and keeping projects on track. When you’re structure isn’t working, developers might find it difficult to access the people and information they need to be successful. Our advice? Start with just one organization on GitHub populated with a hierarchy of teams, them grow from there if necessary.
When organizing repositories, there are three main elements you’ll have to manage consistently: documentation, contributions, and releases. By maintaining control of these communication outlets—and discouraging sprawl—you’ll be able to keep all team members updated on your projects’ progress. Greater visibility also helps new developers get up to speed and start contributing faster.
Task lists, labels, milestones, and project boards can help you organize any GitHub project. Each of these represents different strategies you can use to start new tasks, assign work, or gently remind teams about outstanding issues. For example, task lists are easy to add to comments within issues, and your team can sort issues by project keywords and status with labels. Project boards act as high-level guides to an entire project, linking people to various tasks and issues from one central location.