Updating the non-public workflow template docs (#60404)

Co-authored-by: Sarita Iyer <66540150+saritai@users.noreply.github.com>

Author: salilsub

content/actions/how-tos/reuse-automations/create-workflow-templates.md

@@ -24,7 +24,7 @@ category:
 
 This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the workflow templates will be presented to users when they are creating a new workflow.
 
-1. If it doesn't already exist, create a new repository named `.github` in your organization.
+1. If it doesn't already exist, create a new {% ifversion actions-nga %} {% else %}public {% endif %}repository named `.github` in your organization.
 1. Create a directory named `workflow-templates`.
 1. Create your new workflow file inside the `workflow-templates` directory.
 

content/actions/reference/workflows-and-actions/reusing-workflow-configurations.md

@@ -115,6 +115,7 @@ When a reusable workflow is triggered by a caller workflow, the `github` context
 
 Reference information to use when creating workflow templates for your organization.
 
+{% ifversion actions-nga %}
 ### Workflow template availability
 
 You can use templates in repositories that match or have more restricted visibility than the template repository.
@@ -132,6 +133,7 @@ Because public workflow templates require a public `.github` repository, they ar
 ### Granting access for private/internal repositories
 
 If you're using a private or internal `.github` repository, you need to grant Read access to users or teams who should be able to use the templates.
+{% endif %}
 
 ### The `$default-branch` placeholder
 

data/features/actions-nga.yml

@@ -0,0 +1,5 @@
+# New feature: actions-nga
+# Versioning for Actions NGA (Next Generation Architecture) features
+versions:
+  fpt: '*'
+  ghec: '*'