Skip to content

Issue templates bug_fix.md and improvement.md do not appear in the issue chooser #224

Closed

Description

@PandaeDo

.github/ISSUE_TEMPLATE/bug_fix.md and .github/ISSUE_TEMPLATE/improvement.md start with the license comment; the YAML front matter (name, about, …) follows it. GitHub recognises the metadata only at the very beginning of the file, so neither template is offered in the issue chooser.

Checked: repository.issueTemplates (GraphQL) returns an empty list for this repository.

Fix: put the front matter first and the license comment after it, as REUSE/cr_checker accept a comment below the front matter.

Found by the Copilot review of eclipse-score/contributor_training#2, which carries both files unchanged.

Activity

  1. self-assigned this
    on Oct 29, 2026
  2. self-assigned this
    on Oct 29, 2026
  3. PandaeDo commented on Oct 30, 2026

    @PandaeDo
    ContributorAuthor

    Proposed solution: delete .github/ISSUE_TEMPLATE/bug_fix.md and improvement.md instead of moving their front matter.

    Reason: a repository that has its own .github/ISSUE_TEMPLATE folder does not get the organisation's default issue templates from eclipse-score/.github (GitHub Docs, Creating a default community health file: defaults are used only where the repository has no file of that type). The organisation defines Feature Request, Component Request, Product Increment, Epic, Task and Bug there, with issue types. Today this repository – and every repository created from it – shows none of them, and its own two templates are not recognised either, so its issue chooser offers no form at all. eclipse-score/score, which has no own folder, gets the organisation forms.

    Deleting the folder makes module_template and every new module use the organisation's forms, so they do not drift from them. Moving the front matter instead would keep two templates that duplicate Bug and Task in a weaker form and still hide the organisation's.

    The pull request templates that link to these issue templates (#225) would then point to the organisation's chooser (/issues/new/choose).

  4. added a commit that references this issue on Oct 30, 2026
    07c8442
  5. added a commit that references this issue on Nov 4, 2026
    181b6a0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions