You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we need a way to reference standard community files (like CODE_OF_CONDUCT.md and SECURITY.md) without duplicating them across repositories while ensuring they remain prominently visible on the repository landing page.
Problem
Maintaining multiple copies of community files across repositories creates maintenance overhead
Changes to these documents require updates in multiple places
We want to keep the prominent visibility GitHub provides for these files on repository landing pages
Proposed Solution
Still being investigated
Files to Include
CODE_OF_CONDUCT.md
SECURITY.md
Any other standard community health files we want to centralize
Acceptance Criteria
Community files are stored in a central location
Files are properly linked/referenced/updated in dependent repositories
Files appear prominently on repository landing pages
Background
Currently, we need a way to reference standard community files (like CODE_OF_CONDUCT.md and SECURITY.md) without duplicating them across repositories while ensuring they remain prominently visible on the repository landing page.
Problem
Proposed Solution
Still being investigated
Files to Include
Acceptance Criteria
Resources
The text was updated successfully, but these errors were encountered: