Organization Health Files (.github)

Centralized, org-wide defaults for GitHub. This repository is intended to be named .github at the organization root to provide shared templates and guidance across all repos.

Purpose

• Provide a default pull request template used across repos
• Offer standard issue templates (bug, feature)
• Publish a security policy visible across the org
• Document how inheritance and overrides work

How It Works

• Create an organization repository named .github (exact name).
• Public .github applies to public repos; private .github applies to private repos.
• Files supported for org-wide defaults include /.github/pull_request_template.md, /.github/ISSUE_TEMPLATE/*, SECURITY.md, FUNDING.yml, SUPPORT.md.
• Any repository that has its own local template or policy will override the org default.

Contents

• /.github/pull_request_template.md — Default PR template for all repos without a local override
• /.github/ISSUE_TEMPLATE/bug_report.md — Standard bug report form
• /.github/ISSUE_TEMPLATE/feature_request.md — Standard feature request form
• /.github/ISSUE_TEMPLATE/config.yml — Enables/disables blank issues and adds contact links
• /SECURITY.md — Organization-wide security disclosure policy
• /CODEOWNERS — Sample file for teams; not inherited, use per-repo

Precedence & Limitations

• Repo-level templates take precedence over org defaults.
• CODEOWNERS is not inherited from an org-level .github repo; copy it into each repo that needs it.

Usage

1. Create or update the org .github repository with these files.
2. In any repo without a local template, opening a new PR or issue will pre-fill with the org defaults.
3. Repos can customize by adding their own templates (in repo root, docs/, or .github/).

Customize

• Update contact emails, team names, and links in templates to match your org.
• Adjust labels in issue templates to align with triage workflows.
• Expand with additional templates (e.g., support, RFCs) as needed.

Verification

• Create a test repo without templates; open a PR and an issue to confirm defaults appear.
• Add a local template there to verify it overrides the org default.