From fb28a07df179d17ff2cdfac75607c3f598219cd8 Mon Sep 17 00:00:00 2001 From: Janice Date: Tue, 12 Jul 2022 19:53:42 +0200 Subject: [PATCH] Update content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md --- .../about-issue-and-pull-request-templates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md index eda7e6b8b7..c72af1ee61 100644 --- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md +++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md @@ -42,7 +42,7 @@ Issue templates are stored on the repository's default branch, in a hidden `.git It is possible to manually create a single issue template in Markdown using the legacy issue template workflow, and project contributors will automatically see the template's contents in the issue body. However, we recommend using the upgraded multiple issue template builder{% ifversion fpt or ghec %} or issue forms{% endif %} to create issue templates. For more information about the legacy workflow, see "[Manually creating a single issue template for your repository](/articles/manually-creating-a-single-issue-template-for-your-repository)." -{% data reusables.repositories.security-guidelines %} A link to this policy will be displayed alongside the issue templates in the template chooser. +{% data reusables.repositories.security-guidelines %} ## Pull request templates