Skip to content

Org-wide community health files: issue_template does not cascade; health_percentage stuck at 75% #6

Description

@cryptoxdog

Summary

Auditing Quantum-L9/Cursor-Governance's community profile (gh api repos/Quantum-L9/Cursor-Governance/community/profile) surfaced a gap in this repo's org-wide default coverage.

Finding

"issue_template": null,
"license": null,
  • .github/.github/ISSUE_TEMPLATE/ exists in this repo, but nested under .github/.github/ it only applies to the .github repo itself — it does not cascade org-wide as a default for other Quantum-L9 repos. GitHub's org-wide default mechanism requires ISSUE_TEMPLATE/ at the true root of this repo (or via a .github/ subfolder off the root, not .github/.github/) to fall through to repos without their own copy.
  • license has no org-wide fallback mechanism at all — GitHub does not support a default LICENSE the way it supports CODE_OF_CONDUCT.md/CONTRIBUTING.md/SECURITY.md/SUPPORT.md/PULL_REQUEST_TEMPLATE.md. Every repo needs its own regardless.

Net effect: Cursor-Governance's community-profile health_percentage is capped at 75%, docked specifically for these two, even though CODE_OF_CONDUCT.md, CONTRIBUTING.md, PULL_REQUEST_TEMPLATE.md, and (implicitly) SECURITY.md/SUPPORT.md all resolve correctly to this repo's root copies.

Suggested fix

  1. Move (or duplicate) ISSUE_TEMPLATE/ from .github/.github/ISSUE_TEMPLATE/ to this repo's true root ISSUE_TEMPLATE/ (or root .github/ISSUE_TEMPLATE/) so it cascades org-wide as documented by GitHub.
  2. Decide + document an org policy on LICENSE — since it can't cascade, either publish a recommended default license text in a doc (e.g. LICENSING_POLICY.md) for repo owners to copy in manually, or accept that each repo's LICENSE is a per-repo decision with no org default.

Reference

Confirmed via:

gh api repos/Quantum-L9/Cursor-Governance/community/profile

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions