Skip to content

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

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

Description

@jmrplens
jmrplens
opened on Sep 12, 2026

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

  1. jencarlucci
    added
    feature
    on Sep 14, 2026

  2. donbaroag-sys commented on Sep 17, 2026

    @donbaroag-sys
    donbaroag-sys
    on Sep 17, 2026

    Yoyo

  3. MTL1010000101 commented on Sep 21, 2026

    @MTL1010000101
    MTL1010000101
    on Sep 21, 2026

    Yoyo

  4. MTL1010000101 commented on Sep 24, 2026

    @MTL1010000101
    MTL1010000101
    on Sep 24, 2026

    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

  5. MTL1010000101 commented on Sep 24, 2026

    @MTL1010000101
    MTL1010000101
    on Sep 24, 2026

    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

  6. MTL1010000101 commented on Sep 28, 2026

    @MTL1010000101
    MTL1010000101
    on Sep 28, 2026

    IATA Upgrades Travel Industry Designator Service (TIDS)-国际航协TIDS项目升级通知.pdf my company currency ISO 20022 , EFT STOCK MAERKET , WALLET ISO27001 , BUT YOU SAID MY MONEY ( SCMER )

  7. MTL1010000101 commented on Sep 30, 2026

    @MTL1010000101
    MTL1010000101
    on Sep 30, 2026

    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

    why you said my
    Company money crency schemm?
    , PIV-201 OMB M19-17 SP800-63 ISO 20022 MOMIN TRADING LTD.
    Managing director Company swift code MT-103
    Air aviation industry EFT stock 📈 mono is scams?
    Solved now
    Beat regard
    Managing director
    MD. MOKHLESUR RAHMAN
    WALLET BUDGETBAKERS ISO27001

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

    feature

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions