GitHub does support multiple pull-request templates, but they must be placed inside a .github/PULL_REQUEST_TEMPLATE/ directory. Any Markdown files inside that folder will appear in a dropdown selector when creating a new pull request. The reason you only saw PULL_REQUEST_TEMPLATE.md work is that a single template file at the root of .github/ or under .github/PULL_REQUEST_TEMPLATE.md becomes the default template, while multiple selectable templates must be stored as separate files inside the dedicated folder. The correct structure is:

.github/
└── PULL_REQUEST_TEMPLATE/
├── bug_fix.md
├── feature_request.md
└── documentation_update.md

Once this structure is in place, GitHub will automatically show the dropdown so contributors can choose the appropriate PR template.

Although, GitHub only loads a single default PULL_REQUEST_TEMPLATE.md when it’s placed directly in the .github directory, which is why only that file worked for you. If you want multiple selectable PR templates, they must be placed inside a folder named .github/PULL_REQUEST_TEMPLATE/. Each Markdown file inside that folder becomes its own option in the pull-request template dropdown. For example: .github/PULL_REQUEST_TEMPLATE/bug_fix.md, feature_request.md, and docs_update.md. Once you use this structure, GitHub will automatically display all templates for selection when opening a new pull request.

Why GitHub doesn’t support multiple selectable PR templates

• PR templates are not a “form system”

GitHub PR templates are:

Plain Markdown files

Automatically injected into the PR description

Not interactive (no UI, no logic, no dropdowns)

GitHub’s design goal was:

“Provide a default starting point, not a configurable workflow.”

Because of this:

No dropdown

No chooser UI

No conditionals

No enforcement logic