Feature Request: Support for Default Community Health Files in Internal scoped .github Repository #151827
Replies: 2 comments 2 replies
-
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Bryonsell.com |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
I would like to request the ability to use default community health files (e.g., CONTRIBUTING.md, CODE_OF_CONDUCT.md, etc.) from an internal .github repository. Currently, this functionality is only available for public .github repositories, which limits its use in organizations that require internal repository visibility for compliance or security reasons.
This feature would allow organizations to centralize and standardize community health files across repositories while maintaining internal visibility. It would be especially beneficial for organizations that manage a large number of repositories and need to enforce consistent contribution guidelines, security policies, and other community standards without making the .github repository public.
Thank you for considering this enhancement to improve GitHub's flexibility for organizations with stricter visibility requirements.
Beta Was this translation helpful? Give feedback.
All reactions