Now it is possible to create many levels of nested teams to reflect your company's hierarchy at your GitHub account. It will make your team's structure easier to control.
Practice of merging all developer working copies to a shared mainline several times a day.
Junior teams inherit their parent's permissions, so repository permissions and mentioning among teams in one nest works from top to bottom. If your team structure, for example, is Teamleads>Project Managers>App. Engineering>QA Testers, granting App. Engineering access for some repository means that QA Testers will receive access too. And if QA Testers team will be mentioned, only they will receive a notifications.
But membership inheritance isn't automatic. If you are a member of App. Engineering team and someone will create a juniour team "Automation", members of App. Engineering aren't automatically the members of Automation. Automation and all other teams created under the App. Engineering will inherit permissions and mentions but nothing else.
Great feature! Now it is possible to create really comfy and clear team structure. It will help big companies to better organize their workflow. At Evrone, we work at few big project simultaneously, and sometimes we got a mishmash instead of good structure. This feature will allow to solve this issue.
Chief Front-End Developer at Evrone
You can more information in the docs. Start structure your teams now!
Nested teams are now added to GitHub. It will allow you to reflect your company’s hierarchy at your GitHub account. Additionally, it will make your team’s structure easier to control. Please, provide us with your opinion about this feature in survey, listed below. Your opinion is very important for us and for the community. Maybe, it will be also interesting for you to see the results of the survey.