Repo sync

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md

@@ -22,15 +22,15 @@ shortTitle: Configure
 {% data reusables.repositories.sidebar-settings %}
 1. In the "Features" section, under **Issues**, click **Set up templates**. You may need to enable **Issues** and refresh the page before you can see the button.
 
-![Screenshot of the "Features" section of a repository's settings, with the "Issues" setting ticked and the green "Set up templates" button visible.](/assets/images/help/repository/set-up-issue-templates-button.png)
+   ![Screenshot of the "Features" section of a repository's settings, with the "Issues" setting ticked and the green "Set up templates" button visible.](/assets/images/help/repository/set-up-issue-templates-button.png)
 1. Use the **Add template** dropdown menu, and click on the type of template you'd like to create.
 
    ![Screenshot of the "Add template" dropdown menu expanded to show standard templates, "Bug report" and "Feature request," with a "Custom template".](/assets/images/help/repository/add-template-drop-down-menu.png)
 1. To preview or edit the template before committing it to the repository, next to the template, click **Preview and edit**.
 1. To edit the template, click {% octicon "pencil" aria-label="Edit template" %}, and type in the fields to edit their contents.
 
    ![Screenshot of the preview of an issue template. To the right of the template name, a pencil icon is outlined in dark orange.](/assets/images/help/repository/issue-template-edit-button.png)
-1. To automatically set a default issue title, assign the issue to people with read access to the repository, or apply labels to issues raised from the template, use the fields under "Optional additional information." You can also add these details in the issue template with `title`, `labels`, or `assignees` in a YAML frontmatter format.
+1. To automatically set a default issue title, assign the issue to people with read access to the repository, or apply labels to issues raised from the template, use the fields under "Optional additional information." You can also add these details in the issue template with `title`, `labels`, `type`, or `assignees` in a YAML frontmatter format.
 1. When you're finished editing and previewing your template, click **Propose changes** in the upper right corner of the page.
 1. In the "Commit message" field, type a commit message describing your changes.
 1. Below the commit message fields, select whether to commit your template directly to the default branch, or to create a new branch and open a pull request. For more information about pull requests, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).

content/enterprise-onboarding/index.md

@@ -40,6 +40,26 @@ journeyTracks:
       - '/enterprise-onboarding/support-for-your-enterprise/understanding-support'
       - '/enterprise-onboarding/support-for-your-enterprise/using-the-support-portal'
       - '/enterprise-onboarding/support-for-your-enterprise/managing-support-entitlements'
+  - id: 'github_actions'
+    title: 'Getting started with GitHub Actions'
+    description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} for your enterprise.'
+    guides:
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/about-github-actions-for-enterprises'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/understanding-github-actions'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/security-hardening-for-github-actions'
+      - '/enterprise-onboarding/github-actions-for-your-enterprise/about-billing-for-github-actions'
+  - id: 'feature_enhancements'
+    title: 'Enhancing your experience'
+    description: 'Take advantage of features available with {% data variables.product.prodname_ghe_cloud %}.'
+    guides:
+      - '/enterprise-onboarding/feature-enhancements/about-the-audit-log-for-your-enterprise'
+      - '/enterprise-onboarding/feature-enhancements/about-access-permissions-on-github'
+      - '/enterprise-onboarding/feature-enhancements/about-rulesets'
+      - '/enterprise-onboarding/feature-enhancements/create-a-readme-for-your-enterprise'
+      - '/enterprise-onboarding/feature-enhancements/about-enterprise-security'
 versions:
   ghec: '*'
 topics:

data/reusables/community/issue-forms-sample.md

@@ -5,7 +5,8 @@ title: "[Bug]: "
 labels: ["bug", "triage"]
 projects: ["octo-org/1", "octo-org/44"]
 assignees:
-  - octocat
+  - octocat{% ifversion issue-types %}
+type: bug{% endif %}
 body:
   - type: markdown
     attributes:
@@ -59,7 +60,7 @@ body:
     id: terms
     attributes:
       label: Code of Conduct
-      description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com). 
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com).
       options:
         - label: I agree to follow this project's Code of Conduct
           required: true