Update syntax-for-issue-forms.md

[labudis]

Why:

Issues team shipped a change on 12 Feb that enables required fields on private and internal repos as well as public repos.

Closes: #36268

What's being changed (if available, include any code snippets, screenshots, or gifs):

Updating the note copy to reflect the new behavior.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the preview environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

PR Overview

This PR updates the documentation for issue forms to reflect the recent change in functionality from the Issues team. The key change is the updated note that clarifies the support for the required field across public, private, and internal repositories.

Changes

File	Description
content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md	Updated note to indicate that the required field key is now supported in all repository types

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md:25

• [nitpick] Consider revising the note for clarity by removing redundancy and adding an Oxford comma. For example: '> The required field key is now supported in public, private, and internal repositories.'

> The `required` field key is now supported in all types of repositories including public, private and internal repositories.

Tip: Copilot code review supports C#, Go, Java, JavaScript, Markdown, Python, Ruby and TypeScript, with more languages coming soon. Learn more

[github-actions]

👓 How to review these changes

Thank you for your contribution. To review these changes, you can:

1. Spin up a codespace
2. Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

⚠️ Warning: Our review server is experiencing latency issues.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on the review server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10

---

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server
This table is posted from the Content Changes Table Comment workflow.

🤖 This comment is automatically generated.

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡