Renaming an org team could use a better description about consequences

[kyle-west]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Body

My organization moves people around between teams frequently. Org Teams is a great way to manage code permissions for us and we rely on it heavily. However, several times a year, a few teams will get renamed.

When renaming a team in GitHub, currently, the description text warns that mentions will be broken. This is great, but one thing nearly everyone at my company forgets about is that CODEOWNERS is included in that @mentions scope. We have found that teams rename themselves without realizing that they broke several CODEOWNERS files. This is especially true for repositories that have multiple code owners.

Also as an added help, it might be good to add a link to all the current mentions of the team inside of CODEOWNERS files. Every time a team changes their name, they should run a search for org:my-org path:**/CODEOWNERS @my-org/team-name. Having a link to that search in context would be extremely helpful.

Current wording	Mockup of my suggestions

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐