repo sync

content/actions/quickstart.md

@@ -75,3 +75,69 @@ The super-linter workflow you just added runs any time code is pushed to your re
 - "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial
 - "[Guides](/actions/guides)" for specific uses cases and examples
 - [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action
+
+<div id="quickstart-treatment" hidden>
+
+### Introduction
+
+Printing "Hello, World!" is a great way to explore the basic set up and syntax of a new programming language. In this guide, you'll use GitHub Actions to print "Hello, World!" within your {% data variables.product.prodname_dotcom %} repository's workflow logs. All you need to get started is a {% data variables.product.prodname_dotcom %} repository where you feel comfortable creating and running a sample {% data variables.product.prodname_actions %} workflow. Feel free to create a new repository for this Quickstart, you can use it to test this and future {% data variables.product.prodname_actions %} workflows.
+
+### Creating your first workflow
+
+1. From your repository on {% data variables.product.prodname_dotcom %}, create a new file in the `.github/workflows` directory named `hello-world.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)."
+2. Copy the following YAML contents into the `hello-world.yml` file.
+    {% raw %}
+    ```yaml{:copy}
+    name: Say hello!
+
+    # GitHub Actions Workflows are automatically triggered by GitHub events
+    on:
+      # For this workflow, we're using the workflow_dispatch event which is triggered when the user clicks Run workflow in the GitHub Actions UI
+      workflow_dispatch:
+        # The workflow_dispatch event accepts optional inputs so you can customize the behavior of the workflow
+        inputs:
+          name:
+            description: 'Person to greet'
+            required: true
+            default: 'World'
+    # When the event is triggered, GitHub Actions will run the jobs indicated
+    jobs:
+      say_hello:
+        # Uses a ubuntu-lates runner to complete the requested steps
+        runs-on: ubuntu-latest
+        steps:
+        - run: |
+            echo "Hello ${{ github.event.inputs.name }}!"
+    ```
+    {% endraw %}
+3. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
+    ![Commit workflow file](/assets/images/help/repository/commit-hello-world-file.png)
+4. Once the pull request has been merged, you'll be ready to move on to "Trigger your workflow".
+
+### Trigger your workflow
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workfow you want to run.
+   ![Select say hello job](/assets/images/help/repository/say-hello-job.png)
+1. On the right, click the **Run workflow** drop-down and click **Run workflow**. Optionally, you can enter a custom message into the "Person to greet" input before running the workflow.
+   ![Trigger the manual workflow](/assets/images/help/repository/manual-workflow-trigger.png)
+1. The workflow run will appear at the top of the list of "Say hello!" workflow runs. Click "Say hello!" to see the result of the workflow run.
+   ![Workflow run result listing](/assets/images/help/repository/workflow-run-listing.png)
+1. In the left sidebar, click the "say_hello" job.
+   ![Workflow job listing](/assets/images/help/repository/workflow-job-listing.png)
+1. In the workflow logs, expand the 'Run echo "Hello World!"' section.
+   ![Workflow detail](/assets/images/help/repository/workflow-log-listing.png)
+
+### More starter workflows
+
+{% data variables.product.prodname_dotcom %} provides preconfigured workflow templates that you can start from to automate or create a continuous integration workflows. You can browse the full list of workflow templates in the {% if currentVersion == "free-pro-team@latest" %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}.
+
+### Next steps
+
+The hello-world workflow you just added is a simple example of a manually triggered workflow. This is only the beginning of what you can do with {% data variables.product.prodname_actions %}. Your repository can contain multiple workflows that trigger different jobs based on different events. {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}:
+
+- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial
+- "[Guides](/actions/guides)" for specific uses cases and examples
+
+</div>

content/github/administering-a-repository/about-secret-scanning.md

@@ -1,6 +1,7 @@
 ---
 title: About secret scanning
 intro: '{% data variables.product.product_name %} scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally.'
+product: '{% data reusables.gated-features.secret-scanning %}'
 redirect_from:
   - /github/administering-a-repository/about-token-scanning
   - /articles/about-token-scanning

content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md

@@ -1,6 +1,7 @@
 ---
 title: Configuring secret scanning for private repositories
 intro: 'You can configure how {% data variables.product.product_name %} scans your private repositories for secrets.'
+product: '{% data reusables.gated-features.secret-scanning %}'
 permissions: 'People with admin permissions to a private repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.'
 versions:
   free-pro-team: '*'

content/github/administering-a-repository/managing-alerts-from-secret-scanning.md

@@ -1,6 +1,7 @@
 ---
 title: Managing alerts from secret scanning
 intro: You can view and close alerts for secrets checked in to your repository.
+product: '{% data reusables.gated-features.secret-scanning %}'
 versions:
   free-pro-team: '*'
 ---

content/github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization.md

@@ -1,6 +1,7 @@
 ---
 title: Managing secret scanning for your organization
 intro: 'You can control which repositories in your organization {% data variables.product.product_name %} will scan for secrets.'
+product: '{% data reusables.gated-features.secret-scanning %}'
 permissions: 'Organization owners can manage {% data variables.product.prodname_secret_scanning %} for repositories in the organization.'
 versions:
   free-pro-team: '*'

data/reusables/gated-features/secret-scanning.md

@@ -0,0 +1 @@
+{% data variables.product.prodname_secret_scanning_caps %} is available in public repositories, and in private repositories owned by organizations with an {% data variables.product.prodname_advanced_security %} license. {% data reusables.gated-features.more-info %}

data/reusables/secret-scanning/beta.md

@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta and subject to change. To request access to the beta, [join the waitlist](https://github.com/features/security/advanced-security/signup).
+**Note:** {% data variables.product.prodname_secret_scanning_caps %} for private repositories is currently in beta and subject to change.
 
 {% endnote %}

javascripts/experiment.js

@@ -41,4 +41,21 @@ export default function () {
   // const xbucket = bucket(testName)
   // if (xbucket === TREATMENT) { ... }
   // x.addEventListener('click', evt => evt.preventDefault(); await sendSuccess(testName); evt())
+
+  const treatment = document.getElementById('quickstart-treatment')
+  if (!treatment) return
+
+  const testName = 'quickstart-hello'
+  const xbucket = bucket(testName)
+
+  if (xbucket === TREATMENT) {
+    Array.from(
+      document.querySelectorAll('#article-contents > *')
+    ).forEach(el => { el.hidden = true })
+    treatment.hidden = false
+  }
+
+  document.documentElement.addEventListener('copy', () => {
+    sendSuccess(testName)
+  })
 }