Skip to content

Commit 0886a39

Browse files
graceparkgracepark
authored
Part 4: Update data dir from dash to asterisk (#51098)
1 parent e3a169c commit 0886a39

File tree

309 files changed

+1199
-1199
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

309 files changed

+1199
-1199
lines changed

‎data/reusables/accounts/marketing-emails.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{% data variables.product.product_name %} occasionally sends the following types of marketing emails:
22

3-
- Tips and tricks for getting started with your account
4-
- Customized information about engaging projects or new features
5-
- Newsletters that you've subscribed to
3+
* Tips and tricks for getting started with your account
4+
* Customized information about engaging projects or new features
5+
* Newsletters that you've subscribed to

‎data/reusables/accounts/unlinking-email-address.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
1. To begin unlinking an email address from the locked account, click **Start unlinking email**.
22
1. On the "Unlink Email" screen, click **Continue**.
33
1. In the inbox of the email account you want to unlink, open the email with the subject "[{% data variables.product.company_short %}] Unlink this email."
4-
- Optionally, to unlink multiple email accounts, in the inbox of each account you want to unlink, open the email with the subject "[{% data variables.product.company_short %}] Unlink this email," then complete the following steps.
4+
* Optionally, to unlink multiple email accounts, in the inbox of each account you want to unlink, open the email with the subject "[{% data variables.product.company_short %}] Unlink this email," then complete the following steps.
55

66
1. In the email, click **Unlink this email**.
77

‎data/reusables/actions/about-actions-usage-metrics.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{% data variables.product.prodname_actions %} usage metrics enable you to analyze how your organization is using Actions minutes. You can view usage information related to:
22

3-
- **Workflows**. View usage data for each workflow in your organization, and use this information to identify opportunities for optimization, such as refactoring a workflow or using a {% data variables.actions.hosted_runner %}.
4-
- **Jobs**. See which jobs are the most resource-intensive and where they are running.
5-
- **Repositories**. Get a high-level snapshot of each repository in your organization and their volume of Actions minutes usage.
6-
- **Runtime OS**. Understand how runners for each operating system are using Actions minutes and what types of operating systems your workflows are running on most often.
7-
- **Runner type**. Compare how your self-hosted runners and GitHub-hosted runners use Actions minutes and the volume of workflow runs for each type of runner.
3+
* **Workflows**. View usage data for each workflow in your organization, and use this information to identify opportunities for optimization, such as refactoring a workflow or using a {% data variables.actions.hosted_runner %}.
4+
* **Jobs**. See which jobs are the most resource-intensive and where they are running.
5+
* **Repositories**. Get a high-level snapshot of each repository in your organization and their volume of Actions minutes usage.
6+
* **Runtime OS**. Understand how runners for each operating system are using Actions minutes and what types of operating systems your workflows are running on most often.
7+
* **Runner type**. Compare how your self-hosted runners and GitHub-hosted runners use Actions minutes and the volume of workflow runs for each type of runner.

‎data/reusables/actions/about-artifact-attestations.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@ Artifact attestations enable you to create unfalsifiable provenance and integrit
22

33
When you generate artifact attestations with your software, you create cryptographically signed claims that establish your build's provenance and include the following information:
44

5-
- A link to the workflow associated with the artifact.
6-
- The repository, organization, environment, commit SHA, and triggering event for the artifact.
7-
- Other information from the OIDC token used to establish provenance. For more information, see "[AUTOTITLE](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."
5+
* A link to the workflow associated with the artifact.
6+
* The repository, organization, environment, commit SHA, and triggering event for the artifact.
7+
* Other information from the OIDC token used to establish provenance. For more information, see "[AUTOTITLE](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."
88

99
You can also generate artifact attestations that include an associated software bill of materials (SBOM). Associating your builds with a list of the open source dependencies used in them provides transparency and enables consumers to comply with data protection standards.

‎data/reusables/actions/about-artifact-log-retention.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ By default, the artifacts and log files generated by workflows are retained for
33
{%- ifversion fpt or ghec %}
44
You can adjust the retention period, depending on the type of repository:
55

6-
- For public repositories: you can change this retention period to anywhere between 1 day or 90 days.
7-
- For private{% ifversion ghec %} and internal{% endif %} repositories: you can change this retention period to anywhere between 1 day or 400 days.
6+
* For public repositories: you can change this retention period to anywhere between 1 day or 90 days.
7+
* For private{% ifversion ghec %} and internal{% endif %} repositories: you can change this retention period to anywhere between 1 day or 400 days.
88
{%- else %}
99
You can change this retention period to anywhere between 1 day or 400 days.
1010
{%- endif %}

‎data/reusables/actions/about-larger-runners.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
Customers on {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} plans can choose from a range of managed virtual machines that have more resources than the [standard {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). These machines are referred to as "{% data variables.actions.hosted_runner %}." They offer the following advanced features:
22

3-
- More RAM, CPU, and disk space
4-
- Static IP addresses
5-
- The ability to group runners
6-
- Autoscaling to support concurrent workflows
7-
- GPU-powered and ARM-powered runners
3+
* More RAM, CPU, and disk space
4+
* Static IP addresses
5+
* The ability to group runners
6+
* Autoscaling to support concurrent workflows
7+
* GPU-powered and ARM-powered runners
88

99
These {% data variables.actions.hosted_runners %} are hosted by {% data variables.product.prodname_dotcom %} and have the runner application and other tools preinstalled.

‎data/reusables/actions/about-triggers.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
Workflow triggers are events that cause a workflow to run. These events can be:
22

3-
- Events that occur in your workflow's repository
4-
- Events that occur outside of {% data variables.product.product_name %} and trigger a `repository_dispatch` event on {% data variables.product.product_name %}
5-
- Scheduled times
6-
- Manual
3+
* Events that occur in your workflow's repository
4+
* Events that occur outside of {% data variables.product.product_name %} and trigger a `repository_dispatch` event on {% data variables.product.product_name %}
5+
* Scheduled times
6+
* Manual
77

88
For example, you can configure your workflow to run when a push is made to the default branch of your repository, when a release is created, or when an issue is opened.

‎data/reusables/actions/actions-group-concurrency.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@ To also cancel any currently running job or workflow in the same concurrency gro
66

77
**Notes:**
88

9-
- The concurrency group name is case insensitive. For example, `prod` and `Prod` will be treated as the same concurrency group.
10-
- Ordering is not guaranteed for jobs or workflow runs using concurrency groups. Jobs or workflow runs in the same concurrency group are handled in an arbitrary order.
9+
* The concurrency group name is case insensitive. For example, `prod` and `Prod` will be treated as the same concurrency group.
10+
* Ordering is not guaranteed for jobs or workflow runs using concurrency groups. Jobs or workflow runs in the same concurrency group are handled in an arbitrary order.
1111

1212
{% endnote %}
1313

‎data/reusables/actions/actions-importer-prerequisites.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
- An environment where you can run Linux-based containers, and can install the necessary tools.
2-
- Docker is [installed](https://docs.docker.com/get-docker/) and running.
3-
- [{% data variables.product.prodname_dotcom %} CLI](https://cli.github.com) is installed.
1+
* An environment where you can run Linux-based containers, and can install the necessary tools.
2+
* Docker is [installed](https://docs.docker.com/get-docker/) and running.
3+
* [{% data variables.product.prodname_dotcom %} CLI](https://cli.github.com) is installed.
44

55
{% note %}
66

‎data/reusables/actions/actions-multiple-types.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@ If you specify activity types or filters for an event and your workflow triggers
22

33
For example, a workflow with the following `on` value will run when:
44

5-
- A label is created
6-
- A push is made to the `main` branch in the repository
7-
- A push is made to a {% data variables.product.prodname_pages %}-enabled branch
5+
* A label is created
6+
* A push is made to the `main` branch in the repository
7+
* A push is made to a {% data variables.product.prodname_pages %}-enabled branch
88

99
```yaml
1010
on:

‎data/reusables/actions/actions-secrets-and-variables-naming.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
- Names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
2-
- Names must not start with the `GITHUB_` prefix.
3-
- Names must not start with a number.
4-
- Names are case insensitive.
5-
- Names must be unique at the level they are created at.
1+
* Names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
2+
* Names must not start with the `GITHUB_` prefix.
3+
* Names must not start with a number.
4+
* Names are case insensitive.
5+
* Names must be unique at the level they are created at.

‎data/reusables/actions/add-hosted-runner.md

+9-9
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
1. Click **New runner**, then click **{% octicon "mark-github" aria-label="New hosted runner" %} New {% data variables.product.prodname_dotcom %}-hosted runner**.
22
1. Complete the required details to configure your new runner:
33

4-
- **Name**: Enter a name for your new runner. For easier identification, this should indicate its hardware and operating configuration, such as `ubuntu-20.04-16core`.
5-
- **Platform**: Choose a platform from the available options. Once you've selected a platform, you will be able to choose a specific image.
6-
- **Image**: Choose an image from the available options. Once you've selected an image, you will be able to choose a specific size.
7-
- **GitHub-owned**: For images managed by GitHub, select an image under this tab.
8-
- **Partner**: For images managed by a partner, select an image under this tab. Windows 11 desktop and GPU-optimized images are located under this tab.
9-
- **Size**: Choose a hardware configuration from the list of available options. The available sizes depend on the image that you selected in a previous step. For GPU runners, select a size under the **GPU-powered** tab.
10-
- **Maximum concurrency**: Choose the maximum number of jobs that can be active at any time.
11-
- **Runner group**: Choose the group that your runner will be a member of. This group will host multiple instances of your runner, as they scale up and down to suit demand. {% ifversion ghec %}
12-
- **Networking**: Choose whether static IP address ranges will be assigned to instances of the {% data variables.actions.hosted_runner %}. You can use up to 10 {% data variables.actions.hosted_runner %}s with static IP addresses in total. {% endif %}
4+
* **Name**: Enter a name for your new runner. For easier identification, this should indicate its hardware and operating configuration, such as `ubuntu-20.04-16core`.
5+
* **Platform**: Choose a platform from the available options. Once you've selected a platform, you will be able to choose a specific image.
6+
* **Image**: Choose an image from the available options. Once you've selected an image, you will be able to choose a specific size.
7+
* **GitHub-owned**: For images managed by GitHub, select an image under this tab.
8+
* **Partner**: For images managed by a partner, select an image under this tab. Windows 11 desktop and GPU-optimized images are located under this tab.
9+
* **Size**: Choose a hardware configuration from the list of available options. The available sizes depend on the image that you selected in a previous step. For GPU runners, select a size under the **GPU-powered** tab.
10+
* **Maximum concurrency**: Choose the maximum number of jobs that can be active at any time.
11+
* **Runner group**: Choose the group that your runner will be a member of. This group will host multiple instances of your runner, as they scale up and down to suit demand. {% ifversion ghec %}
12+
* **Networking**: Choose whether static IP address ranges will be assigned to instances of the {% data variables.actions.hosted_runner %}. You can use up to 10 {% data variables.actions.hosted_runner %}s with static IP addresses in total. {% endif %}
1313

1414
{% data reusables.actions.larger-runner-name-note %}
1515

‎data/reusables/actions/allow-specific-actions-intro.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,15 @@ When you choose {% data reusables.actions.policy-label-for-select-actions-workfl
77

88
{% data reusables.repositories.settings-permissions-org-policy-note %}
99

10-
- **Allow actions created by {% data variables.product.prodname_dotcom %}:** You can allow all actions created by {% data variables.product.prodname_dotcom %} to be used by workflows. Actions created by {% data variables.product.prodname_dotcom %} are located in the `actions` and `github` organizations. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.
11-
- **Allow Marketplace actions by verified creators:** {% ifversion ghes %}This option is available if you have {% data variables.product.prodname_github_connect %} enabled and configured with {% data variables.product.prodname_actions %}. For more information, see "[AUTOTITLE](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)."{% endif %} You can allow all {% data variables.product.prodname_marketplace %} actions created by verified creators to be used by workflows. When GitHub has verified the creator of the action as a partner organization, the {% octicon "verified" aria-label="The verified badge" %} badge is displayed next to the action in {% data variables.product.prodname_marketplace %}.
12-
- **Allow specified actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}:** You can restrict workflows to use actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} in specific organizations and repositories. Specified actions cannot be set to more than 1000.
10+
* **Allow actions created by {% data variables.product.prodname_dotcom %}:** You can allow all actions created by {% data variables.product.prodname_dotcom %} to be used by workflows. Actions created by {% data variables.product.prodname_dotcom %} are located in the `actions` and `github` organizations. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.
11+
* **Allow Marketplace actions by verified creators:** {% ifversion ghes %}This option is available if you have {% data variables.product.prodname_github_connect %} enabled and configured with {% data variables.product.prodname_actions %}. For more information, see "[AUTOTITLE](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)."{% endif %} You can allow all {% data variables.product.prodname_marketplace %} actions created by verified creators to be used by workflows. When GitHub has verified the creator of the action as a partner organization, the {% octicon "verified" aria-label="The verified badge" %} badge is displayed next to the action in {% data variables.product.prodname_marketplace %}.
12+
* **Allow specified actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}:** You can restrict workflows to use actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} in specific organizations and repositories. Specified actions cannot be set to more than 1000.
1313

1414
To restrict access to specific tags or commit SHAs of an action{% ifversion actions-workflow-policy %} or reusable workflow{% endif %}, use the same syntax used in the workflow to select the action{% ifversion actions-workflow-policy %} or reusable workflow{% endif %}.
1515

16-
- For an action, the syntax is `OWNER/REPOSITORY@TAG-OR-SHA`. For example, use `actions/[email protected]` to select a tag or `actions/javascript-action@a824008085750b8e136effc585c3cd6082bd575f` to select a SHA. For more information, see "[AUTOTITLE](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions)."
16+
* For an action, the syntax is `OWNER/REPOSITORY@TAG-OR-SHA`. For example, use `actions/[email protected]` to select a tag or `actions/javascript-action@a824008085750b8e136effc585c3cd6082bd575f` to select a SHA. For more information, see "[AUTOTITLE](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions)."
1717
{%- ifversion actions-workflow-policy %}
18-
- For a reusable workflow, the syntax is `OWNER/REPOSITORY/PATH/FILENAME@TAG-OR-SHA`. For example, `octo-org/another-repo/.github/workflows/workflow.yml@v1`. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow)."
18+
* For a reusable workflow, the syntax is `OWNER/REPOSITORY/PATH/FILENAME@TAG-OR-SHA`. For example, `octo-org/another-repo/.github/workflows/workflow.yml@v1`. For more information, see "[AUTOTITLE](/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow)."
1919
{%- endif %}
2020

2121
You can use the `*` wildcard character to match patterns. For example, to allow all actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} in organizations that start with `space-org`, you can specify `space-org*/*`. To allow all actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} in repositories that start with octocat, you can use `*/octocat**@*`. For more information about using the `*` wildcard, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."

‎data/reusables/actions/artifact-attestations-step-for-container-images.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
- name: Generate artifact attestation
1+
* name: Generate artifact attestation
22
uses: actions/attest-build-provenance@v1
33
with:
44
subject-name: {% raw %}${{ env.REGISTRY }}/${{ env.IMAGE_NAME}}{% endraw %}

0 commit comments

Comments
 (0)