Skip to content

[Schema Inaccuracy] community-profile files.issue_template is null for a .github/ISSUE_TEMPLATE/ directory the community page counts #7187

Description

@jmrplens

Schema Inaccuracy

The community-profile schema (GET /repos/{owner}/{repo}/community/profile) describes files.issue_template as a nullable community-health-file, and the operation summary says the response reports "the presence of ISSUE_TEMPLATE, PULL_REQUEST_TEMPLATE, README, and CONTRIBUTING files". At runtime the field is null for every repository whose templates live under .github/ISSUE_TEMPLATE/ (Markdown or YAML issue forms), even though the community profile page marks "Issue templates" as added and health_percentage counts them. The field is only non-null for the single legacy file .github/ISSUE_TEMPLATE.md.

Expected

Either the runtime behavior matches the description (the field reports the same presence the community page and health_percentage use, so a .github/ISSUE_TEMPLATE/ directory counts), or the description of files.issue_template says that it only reports the legacy single file ISSUE_TEMPLATE.md and not a templates directory, so a consumer knows to list the directory instead.

Reproduction Steps

Measured on 2026-09-12 against public repositories:

# .github/ISSUE_TEMPLATE/ holds four YAML issue forms and config.yml; the community page shows 100 % with "Issue templates" added
curl -s -H "Authorization: Bearer $TOKEN" -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/repos/jmrplens/gitlab-mcp-server/community/profile | jq '{health_percentage, issue_template: .files.issue_template}'
# {"health_percentage": 100, "issue_template": null}

# .github/ISSUE_TEMPLATE/ holds three Markdown templates
curl -s ... https://api.github.com/repos/cli/cli/community/profile | jq '{health_percentage, issue_template: .files.issue_template}'
# {"health_percentage": 100, "issue_template": null}

# the single legacy file .github/ISSUE_TEMPLATE.md
curl -s ... https://api.github.com/repos/github/gh-ost/community/profile | jq '.files.issue_template.url'
# "https://api.github.com/repos/github/gh-ost/contents/.github/ISSUE_TEMPLATE.md"

The GraphQL side of the same gap (Repository.issueTemplates omits YAML issue forms and the legacy file) is reported with the full comparison table in the community forum: https://github.com/orgs/community/discussions/207706

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions