jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 03:44:00 -05:00
Code Issues Projects Releases Wiki Activity

Make sure there is a blank line above and below headings (#37922)

Browse Source
This commit is contained in:
Grace Park
2023-06-26 13:24:44 -07:00
committed by GitHub
parent 6b51cec1f9
commit 32af69c277
347 changed files with 1236 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
content/actions/using-workflows/workflow-syntax-for-github-actions.md
View File

@@ -28,6 +28,7 @@ You must store workflow files in the `.github/workflows` directory of your repos
The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's "Actions" tab. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository.
{% ifversion actions-run-name %}
## `run-name`
The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If `run-name` is omitted or is only whitespace, then the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
@@ -512,6 +513,7 @@ jobs:
```
{% ifversion fpt or ghec %}
### Example: Using the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
`docker://{host}/{image}:{tag}`
@@ -527,6 +529,7 @@ jobs:
```
{% endif %}
### Example: Using a Docker public registry action
`docker://{host}/{image}:{tag}`