Multiple issue and pull request templates
Issue and pull request templates help teams gather the right information from the beginning of a thread, but sometimes one template just isn’t enough. Now project maintainers can have and…
Issue and pull request templates help teams gather the right information from the beginning of a thread, but sometimes one template just isn’t enough. Now project maintainers can have and use multiple templates in their repositories.
To add multiple issue templates to a repository create an ISSUE_TEMPLATE/
directory in your project root. Within that ISSUE_TEMPLATE/
directory you can create as many issue templates as you need, for example ISSUE_TEMPLATE/bugs.md
. To use those issue templates add ?template=
and your template name to the new issue URL. Continuing the example, if you create the template bugs.md
you add ?template=bugs.md
to the new issue URL, so it becomes /issues/new?template=bugs.md
.
Your default ISSUE_TEMPLATE.md
files will continue to work as the default when a template isn’t specified in the new issue URL. Pull request templates follow the same pattern: add a directory called PULL_REQUEST_TEMPLATE
to the root directory of your repository, and add the ?template=
to your pull request URLs. And if you’re worried about extra clutter in the root directory of your project, all of these directories work within the .github
folder as well
To read more or learn about additional options, check out the documentation.
Written by
Related posts

Vibe coding with GitHub Copilot: Agent mode and MCP support rolling out to all VS Code users
In celebration of MSFT’s 50th anniversary, we’re rolling out Agent Mode with MCP support to all VS Code users. We are also announcing the new GitHub Copilot Pro+ plan w/ premium requests, the general availability of models from Anthropic, Google, and OpenAI, next edit suggestions for code completions & the Copilot code review agent.

GitHub Availability Report: February 2025
In February, we experienced two incidents that resulted in degraded performance across GitHub services.

GitHub Availability Report: January 2025
In January, we experienced two incidents that resulted in degraded performance across GitHub services.