Using Sub-Teams as Slugs in Combination with Parent Teams #67568
Replies: 2 comments
-
Thanks for posting in the GitHub Community, @juliankasimir ! We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category, the Discussions category is solely related to conversations around the GitHub product Discussions. I've gone ahead and moved it for you. Good luck! |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
As an example, let's say we currently have these team names:
I wanted to ask if it wouldn't make sense if the team name unique identifier was made up of a combination of parent and subteam names?
Then you could instead structure the teams as follows:
Parent Team:
code-owners
Sub-Team:
js
The proposed slug for the Sub-Team would be
code-owners/js
, and we could use it in our CODEOWNERS file like this:*.js @code-owners/js
We have tested it and unfortunately cannot set up a second group as follows, cause e.g. "frontend" still used before.
Beta Was this translation helpful? Give feedback.
All reactions