Skip to content

Commit a050ee5

Browse files
authored
Merge branch 'main' into yamiacat-merge-accounts-patch
2 parents f5d0582 + 64c5f98 commit a050ee5

File tree

14 files changed

+87
-39
lines changed

14 files changed

+87
-39
lines changed
-23.1 KB
Loading
14.1 KB
Loading

content/actions/hosting-your-own-runners/about-self-hosted-runners.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,14 +21,12 @@ A self-hosted runner is a system that you deploy and manage to execute jobs from
2121

2222
{% data reusables.actions.self-hosted-runner-description %} {% data reusables.actions.self-hosted-runner-locations %}
2323

24-
{% data reusables.actions.self-hosted-runner-architecture %} {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
25-
2624
You can add self-hosted runners at various levels in the management hierarchy:
2725
- Repository-level runners are dedicated to a single repository.
2826
- Organization-level runners can process jobs for multiple repositories in an organization.
2927
- Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
3028

31-
Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
29+
{% data reusables.actions.self-hosted-runner-architecture %} {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
3230

3331
{% data reusables.actions.self-hosted-runner-auto-removal %}
3432

content/actions/learn-github-actions/expressions.md

Lines changed: 37 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -366,4 +366,40 @@ For example, consider an array of objects named `fruits`.
366366
]
367367
```
368368

369-
The filter `fruits.*.name` returns the array `[ "apple", "orange", "pear" ]`
369+
The filter `fruits.*.name` returns the array `[ "apple", "orange", "pear" ]`.
370+
371+
You may also use the `*` syntax on an object. For example, suppose you have an object named `vegetables`.
372+
373+
```json
374+
375+
{
376+
"scallions":
377+
{
378+
"colors": ["green", "white", "red"],
379+
"ediblePortions": ["roots", "stalks"],
380+
},
381+
"beets":
382+
{
383+
"colors": ["purple", "red", "gold", "white", "pink"],
384+
"ediblePortions": ["roots", "stems", "leaves"],
385+
},
386+
"artichokes":
387+
{
388+
"colors": ["green", "purple", "red", "black"],
389+
"ediblePortions": ["hearts", "stems", "leaves"],
390+
},
391+
}
392+
```
393+
394+
The filter `vegetables.*.ediblePortions` could evaluate to:
395+
396+
```json
397+
398+
[
399+
["roots", "stalks"],
400+
["hearts", "stems", "leaves"],
401+
["roots", "stems", "leaves"],
402+
]
403+
```
404+
405+
Since objects don't preserve order, the order of the output can not be guaranteed.

content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Organization owners and billing managers can view {% data variables.product.prod
3434
{% data reusables.organizations.billing-settings %}
3535
{% data reusables.dotcom_billing.actions-minutes %}
3636
{% data reusables.dotcom_billing.actions-packages-storage %}
37-
{% data reusables.dotcom_billing.actions-packages-report-download %}
37+
{% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
3838

3939
## Viewing {% data variables.product.prodname_actions %} usage for your enterprise account
4040

content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ topics:
1515

1616
## {% data variables.product.prodname_codespaces %} pricing
1717

18-
{% data variables.product.prodname_codespaces %} usage is billed for all accounts on the Team and Enterprise plans, and does not include any entitlements. Individual accounts are not currently billed for {% data variables.product.prodname_codespaces %} usage.
18+
{% data variables.product.prodname_codespaces %} usage is billed for all organization and enterprise accounts on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %}, which do not include any free minutes or storage. Personal accounts are not currently billed for {% data variables.product.prodname_codespaces %} usage.
1919

2020
{% data variables.product.prodname_codespaces %} usage is billed according to the units of measure in the following table:
2121

content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Organization owners and billing managers can view {% data variables.product.prod
1919

2020
{% data reusables.organizations.billing-settings %}
2121
{% data reusables.dotcom_billing.codespaces-minutes %}
22-
{% data reusables.dotcom_billing.codespaces-report-download %}
22+
{% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
2323

2424
## Viewing {% data variables.product.prodname_codespaces %} usage for your enterprise account
2525

@@ -29,3 +29,5 @@ Enterprise owners and billing managers can view {% data variables.product.prodna
2929
{% data reusables.enterprise-accounts.settings-tab %}
3030
{% data reusables.enterprise-accounts.billing-tab %}
3131
1. Under "{% data variables.product.prodname_codespaces %}", view the usage details of each organization in your enterprise account.
32+
{% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %}
33+

content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Organization owners and billing managers can view {% data variables.product.prod
3333
{% data reusables.organizations.billing-settings %}
3434
{% data reusables.dotcom_billing.packages-data %}
3535
{% data reusables.dotcom_billing.actions-packages-storage %}
36-
{% data reusables.dotcom_billing.actions-packages-report-download %}
36+
{% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
3737

3838
## Viewing {% data variables.product.prodname_registry %} usage for your enterprise account
3939

contributing/content-style-guide.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -365,7 +365,7 @@ steps:
365365
Examples:
366366
- See the code block in "[Publishing to package registries](https://docs.github.com/en/actions/guides/building-and-testing-python#publishing-to-package-registries)"
367367

368-
### Pinning version numbers to SHA
368+
#### Pinning version numbers to SHA
369369

370370
Code examples that use third-party actions must always pin to a full length commit SHA, instead of the version number or branch:
371371

@@ -383,6 +383,14 @@ steps:
383383

384384
For more information, see "[Using SHAs](https://docs.github.com/en/actions/learn-github-actions/finding-and-customizing-actions#using-shas)"
385385

386+
### GitHub Codespaces
387+
388+
Always use "GitHub Codespaces" (`{% data variables.product.prodname_github_codespaces %}`) as the product name, not just "Codespaces". This helps to avoid confusion with "codespaces" (lowercase c), which refers to instances of remote coding workspaces created with GitHub Codespaces.
389+
390+
Always use "dev container" (or, where clarification is needed, its longer form "development container") and not "devcontainer" (one word), except in file/path names. The single word could form could be considered a brand, which we want to avoid, and we also want to be consistent with the two-word form used in [the Visual Studio Code documentation](https://code.visualstudio.com/docs/remote/create-dev-container#_path-to-creating-a-dev-container).
391+
392+
Use "development container configuration files" to refer to all of the files in the `.devcontainer` directory (plus the `.devcontainer.json` if that's being used rather than `devcontainer.json` in the `.devcontainer` directory). Don't refer to these as "development container files" or "devcontainer files" to avoid this being taken as referring to `devcontainer.json` files. "Development container configuration files" refers to all of the files that can be used to configure a dev container, including `Dockerfile` and `docker-compose.yml` files. Don't use "the development container configuration file" (singular) when referring specifically to a `devcontainer.json` file. Instead refer to this file by its name.
393+
386394
## Punctuation
387395

388396
Follow standard American English punctuation rules. For more guidance, see “[Punctuation](https://brand.github.com/content/grammar#punctuation)” in GitHub’s Brand Guide and “[Punctuation](https://docs.microsoft.com/style-guide/punctuation)” in the Microsoft Style Guide.
Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
1. Optionally, next to "Billing & plans", click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %} to the account's primary email address.
2+
![Download CSV report](/assets/images/help/billing/actions-packages-report-download-org.png)

0 commit comments

Comments
 (0)