Skip to content

Implement standard GitHub community health files using repository references #65

Open
@ryancheley

Description

@ryancheley

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    github-actionGitHub Actions related issuegovernanceDefine process, decide on criteria, etc.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @ryancheley

        Issue actions

          Implement standard GitHub community health files using repository references · Issue #65 · django-commons/controls