You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/actions/quickstart.md
+66Lines changed: 66 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -75,3 +75,69 @@ The super-linter workflow you just added runs any time code is pushed to your re
75
75
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial
76
76
- "[Guides](/actions/guides)" for specific uses cases and examples
77
77
- [github/super-linter](https://github.com/github/super-linter) for more details about configuring the Super-Linter action
78
+
79
+
<div id="quickstart-treatment" hidden>
80
+
81
+
### Introduction
82
+
83
+
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.
84
+
85
+
### Creating your first workflow
86
+
87
+
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)."
88
+
2. Copy the following YAML contents into the `hello-world.yml` file.
89
+
{% raw %}
90
+
```yaml{:copy}
91
+
name: Say hello!
92
+
93
+
# GitHub Actions Workflows are automatically triggered by GitHub events
94
+
on:
95
+
# For this workflow, we're using the workflow_dispatch event which is triggered when the user clicks Run workflow in the GitHub Actions UI
96
+
workflow_dispatch:
97
+
# The workflow_dispatch event accepts optional inputs so you can customize the behavior of the workflow
98
+
inputs:
99
+
name:
100
+
description: 'Person to greet'
101
+
required: true
102
+
default: 'World'
103
+
# When the event is triggered, GitHub Actions will run the jobs indicated
104
+
jobs:
105
+
say_hello:
106
+
# Uses a ubuntu-lates runner to complete the requested steps
107
+
runs-on: ubuntu-latest
108
+
steps:
109
+
- run: |
110
+
echo "Hello ${{ github.event.inputs.name }}!"
111
+
```
112
+
{% endraw %}
113
+
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**.
4. Once the pull request has been merged, you'll be ready to move on to "Trigger your workflow".
116
+
117
+
### Trigger your workflow
118
+
119
+
{% data reusables.repositories.navigate-to-repo %}
120
+
{% data reusables.repositories.actions-tab %}
121
+
1. In the left sidebar, click the workfow you want to run.
122
+

123
+
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.
124
+

125
+
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.
126
+

127
+
1. In the left sidebar, click the "say_hello" job.
{% 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 %}.
135
+
136
+
### Next steps
137
+
138
+
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 %}:
139
+
140
+
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial
141
+
- "[Guides](/actions/guides)" for specific uses cases and examples
Copy file name to clipboardExpand all lines: content/github/administering-a-repository/about-secret-scanning.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
---
2
2
title: About secret scanning
3
3
intro: '{% data variables.product.product_name %} scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally.'
4
+
product: '{% data reusables.gated-features.secret-scanning %}'
Copy file name to clipboardExpand all lines: content/github/administering-a-repository/configuring-secret-scanning-for-private-repositories.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
---
2
2
title: Configuring secret scanning for private repositories
3
3
intro: 'You can configure how {% data variables.product.product_name %} scans your private repositories for secrets.'
4
+
product: '{% data reusables.gated-features.secret-scanning %}'
4
5
permissions: 'People with admin permissions to a private repository can enable {% data variables.product.prodname_secret_scanning %} for the repository.'
0 commit comments