Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement standard GitHub community health files using repository references #65

Open
3 tasks
ryancheley opened this issue Nov 30, 2024 · 0 comments
Open
3 tasks
Labels
github-action GitHub Actions related issue governance Define process, decide on criteria, etc.

Comments

@ryancheley
Copy link
Member

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

  • 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

Resources

@ryancheley ryancheley added github-action GitHub Actions related issue governance Define process, decide on criteria, etc. labels Nov 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
github-action GitHub Actions related issue governance Define process, decide on criteria, etc.
Projects
None yet
Development

No branches or pull requests

1 participant