Repository navigation
Add note clarifying feature availability - #11822
Conversation
|
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. |
|
@Maximisch |
lecoursen
left a comment
There was a problem hiding this comment.
👋🏻 @Maximisch, I agree that this would be helpful to clarify! While reviewing this I noticed that "Syntax for issue forms" seems to be repeating this beta information twice:
Adding the new information to the reusable here would lead to even more duplication. 😭 Would you mind removing that product property from the front matter of that article in this PR as well? Thanks!
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
|
|
@lecoursen I removed the product tag as you suggested! 👍 |
|
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 ⚡ |

Why:
Minor adjustment to make feature availability more clear for customers.
People are currently frustrated that this feature cannot be activated for private repositories only (see e.g. here), and this minor note should help avoid future frustration.
What's being changed:
Added the sentence "Issue forms can currently be enabled on private repositories only." to the note box on issue forms.
Check off the following:
Writer impact (This section is for GitHub staff members only):