From 5274e7eaa4670b8d4923a61b0d5fbb3862a97e6d Mon Sep 17 00:00:00 2001 From: Malix - Alix Brunet Date: Sun, 17 May 2026 16:19:42 +0200 Subject: [PATCH] deprecate: `.github/issue_template.md` blank issues template --- .../configuring-issue-templates-for-your-repository.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md index e152f82c1eb1..f5e49f877376 100644 --- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md +++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md @@ -71,9 +71,6 @@ Here is the rendered version of the issue form. You can encourage contributors to use issue templates by setting `blank_issues_enabled` to `false`. If you set `blank_issues_enabled` to `true`, everyone with access to the repository will see the **Blank issue** option in the template chooser. When `blank_issues_enabled` is set to `false`, users with write access or above (Write, Maintain, or Admin roles) will still see the **Blank issue** option in the template chooser, labeled **Maintainers only**. Contributors with Read or Triage roles will only see the configured templates. -> [!NOTE] -> If you used the legacy workflow to manually create an `issue_template.md` file in the `.github` folder and enable blank issues in your _config.yml_ file, the template in `issue_template.md` will be used when people choose to open a blank issue. If you disable blank issues, the template will never be used. - If you prefer to receive certain reports outside of {% data variables.product.github %}, you can direct people to external sites with `contact_links`. Here is an example _config.yml_ file.