зеркало из https://github.com/github/docs.git
Remove spaces from code in content and data (#37382)
Co-authored-by: Laura Coursen <lecoursen@github.com>
This commit is contained in:
Grace Park
GitHub
Родитель
151285093e
Коммит
87900cb264
|
|
@ -122,6 +122,6 @@ jobs:
|
|||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure-kubernetes-service.yml `](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* For the original starter workflow, see [`azure-kubernetes-service.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The actions used to in this workflow are the official Azure [`Azure/login`](https://github.com/Azure/login),[`Azure/aks-set-context`](https://github.com/Azure/aks-set-context), [`Azure/CLI`](https://github.com/Azure/CLI), [`Azure/k8s-bake`](https://github.com/Azure/k8s-bake), and [`Azure/k8s-deploy`](https://github.com/Azure/k8s-deploy)actions.
|
||||
* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
|
||||
|
|
|
|||
|
|
@ -100,7 +100,7 @@ You can create configuration variables for use across multiple workflows, and ca
|
|||
|
||||
For example, you can use configuration variables to set default values for parameters passed to build tools at an organization level, but then allow repository owners to override these parameters on a case-by-case basis.
|
||||
|
||||
When you define configuration variables, they are automatically available in the `vars` context. For more information, see "[Using the `vars `context to access configuration variable values](#using-the-vars-context-to-access-configuration-variable-values)".
|
||||
When you define configuration variables, they are automatically available in the `vars` context. For more information, see "[Using the `vars` context to access configuration variable values](#using-the-vars-context-to-access-configuration-variable-values)".
|
||||
|
||||
### Configuration variable precedence
|
||||
|
||||
|
|
|
|||
|
|
@ -127,7 +127,7 @@ For more information, see "[AUTOTITLE](/actions/using-jobs/using-a-matrix-for-yo
|
|||
|
||||
If your jobs regularly reuse dependencies, you can consider caching these files to help improve performance. Once the cache is created, it is available to all workflows in the same repository.
|
||||
|
||||
This example demonstrates how to cache the ` ~/.npm` directory:
|
||||
This example demonstrates how to cache the `~/.npm` directory:
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
|
|
|
|||
|
|
@ -961,28 +961,28 @@ Before you'll see `git` category actions, you must enable Git events in the audi
|
|||
|
||||
| Action | Description
|
||||
|--------|-------------
|
||||
| `protected_branch.create ` | Branch protection was enabled on a branch.
|
||||
| `protected_branch.create` | Branch protection was enabled on a branch.
|
||||
| `protected_branch.destroy` | Branch protection was disabled on a branch.
|
||||
| `protected_branch.dismiss_stale_reviews ` | Enforcement of dismissing stale pull requests was updated on a branch.
|
||||
| `protected_branch.dismiss_stale_reviews` | Enforcement of dismissing stale pull requests was updated on a branch.
|
||||
{%- ifversion ghes %}
|
||||
| `protected_branch.dismissal_restricted_users_teams` | Enforcement of restricting users and/or teams who can dismiss reviews was updated on a branch.
|
||||
{%- endif %}
|
||||
| `protected_branch.policy_override ` | A branch protection requirement was overridden by a repository administrator.
|
||||
| `protected_branch.rejected_ref_update ` | A branch update attempt was rejected.
|
||||
| `protected_branch.policy_override` | A branch protection requirement was overridden by a repository administrator.
|
||||
| `protected_branch.rejected_ref_update` | A branch update attempt was rejected.
|
||||
| `protected_branch.required_status_override` | The required status checks branch protection requirement was overridden by a repository administrator.
|
||||
| `protected_branch.review_policy_and_required_status_override` | The required reviews and required status checks branch protection requirements were overridden by a repository administrator.
|
||||
| `protected_branch.review_policy_override` | The required reviews branch protection requirement was overridden by a repository administrator.
|
||||
| `protected_branch.update_admin_enforced ` | Branch protection was enforced for repository administrators.
|
||||
| `protected_branch.update_admin_enforced` | Branch protection was enforced for repository administrators.
|
||||
{%- ifversion ghes %}
|
||||
| `protected_branch.update_allow_deletions_enforcement_level` | Enforcement of allowing users with push access to delete matching branches was updated on a branch.
|
||||
| `protected_branch.update_allow_force_pushes_enforcement_level` | Enforcement of allowing force pushes for all users with push access was updated on a branch.
|
||||
| `protected_branch.update_linear_history_requirement_enforcement_level` | Enforcement of requiring linear commit history was updated on a branch.
|
||||
{%- endif %}
|
||||
| `protected_branch.update_pull_request_reviews_enforcement_level ` | Enforcement of required pull request reviews was updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
|
||||
| `protected_branch.update_require_code_owner_review ` | Enforcement of required code owner review was updated on a branch.
|
||||
| `protected_branch.update_pull_request_reviews_enforcement_level` | Enforcement of required pull request reviews was updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
|
||||
| `protected_branch.update_require_code_owner_review` | Enforcement of required code owner review was updated on a branch.
|
||||
| `protected_branch.update_required_approving_review_count` | Enforcement of the required number of approvals before merging was updated on a branch.
|
||||
| `protected_branch.update_required_status_checks_enforcement_level ` | Enforcement of required status checks was updated on a branch.
|
||||
| `protected_branch.update_signature_requirement_enforcement_level ` | Enforcement of required commit signing was updated on a branch.
|
||||
| `protected_branch.update_required_status_checks_enforcement_level` | Enforcement of required status checks was updated on a branch.
|
||||
| `protected_branch.update_signature_requirement_enforcement_level` | Enforcement of required commit signing was updated on a branch.
|
||||
| `protected_branch.update_strict_required_status_checks_policy` | Enforcement of required status checks was updated on a branch.
|
||||
| `protected_branch.update_name` | A branch name pattern was updated for a branch.
|
||||
|
||||
|
|
|
|||
|
|
@ -91,7 +91,7 @@ The `$GITHUB_VIA` variable is available in the pre-receive hook environment when
|
|||
| <pre>git refs update api</pre> | Update of a ref via the API | "[AUTOTITLE](/rest/git#update-a-reference)" in the REST API documentation |
|
||||
| <pre>git repo contents api</pre> | Change to a file's contents via the API | "[AUTOTITLE](/rest/repos#create-or-update-file-contents)" in the REST API documentation |
|
||||
{%- ifversion ghes %}
|
||||
| `merge ` | Merge of a pull request using auto-merge | "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" |
|
||||
| `merge` | Merge of a pull request using auto-merge | "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" |
|
||||
{%- endif %}
|
||||
| <pre>merge base into head</pre> | Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging)" |
|
||||
| <pre>pull request branch delete button</pre> | Deletion of a topic branch from a pull request in the web interface | "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" |
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ You use three different commands to generate results and upload them to {% data
|
|||
|
||||
<!--Option to analyze multiple languages with one call-->
|
||||
1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of each supported programming language in the repository.
|
||||
2. ` database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file.
|
||||
2. `database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file.
|
||||
3. `github upload-results` to upload the resulting SARIF files to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts.
|
||||
|
||||
You can display the command-line help for any command using the <nobr>`--help`</nobr> option.
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ Codespaces are designed to be security hardened by default. To help maintain thi
|
|||
|
||||
### Using secrets to access sensitive information
|
||||
|
||||
Always use encrypted secrets when you want to use sensitive information (such as access tokens) in a codespace. You can access your secrets as environment variables in the codespace, including from the terminal. For example, you can launch a terminal within your codespace and use `echo $SECRET_NAME ` to see the value of a secret.
|
||||
Always use encrypted secrets when you want to use sensitive information (such as access tokens) in a codespace. You can access your secrets as environment variables in the codespace, including from the terminal. For example, you can launch a terminal within your codespace and use `echo $SECRET_NAME` to see the value of a secret.
|
||||
|
||||
The secret values are copied to environment variables whenever the codespace is resumed or created and are also synced when they are changed.
|
||||
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ $ git merge REMOTE-NAME/BRANCH-NAME
|
|||
|
||||
## Pulling changes from a remote repository
|
||||
|
||||
`git pull` is a convenient shortcut for completing both `git fetch` and `git merge `in the same command:
|
||||
`git pull` is a convenient shortcut for completing both `git fetch` and `git merge`in the same command:
|
||||
|
||||
```shell
|
||||
$ git pull REMOTE-NAME BRANCH-NAME
|
||||
|
|
|
|||
|
|
@ -229,7 +229,7 @@ To create a nested list using the web editor on {% data variables.product.produc
|
|||
|
||||
To create a nested list in the comment editor on {% data variables.product.product_name %}, which doesn't use a monospaced font, you can look at the list item immediately above the nested list and count the number of characters that appear before the content of the item. Then type that number of space characters in front of the nested list item.
|
||||
|
||||
In this example, you could add a nested list item under the list item `100. First list item` by indenting the nested list item a minimum of five spaces, since there are five characters (`100. `) before `First list item`.
|
||||
In this example, you could add a nested list item under the list item `100. First list item` by indenting the nested list item a minimum of five spaces, since there are five characters (`100 .`) before `First list item`.
|
||||
|
||||
```markdown
|
||||
100. First list item
|
||||
|
|
|
|||
|
|
@ -352,8 +352,8 @@ For more information, see "[AUTOTITLE](/organizations/managing-organization-sett
|
|||
| `secret_scanning_push_protection_custom_message_updated` | Triggered when an organization owner or admin updates the custom message triggered by an attempted push to a push-protected repository. For more information, see "[AUTOTITLE](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)."
|
||||
{%- endif %}
|
||||
{%- ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| `secret_scanning_push_protection_disable ` | Triggered when an organization owner or person with admin access to the organization disables push protection for {% data variables.product.prodname_secret_scanning %}. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
| `secret_scanning_push_protection_enable ` | Triggered when an organization owner or person with admin access to the organization enables push protection for {% data variables.product.prodname_secret_scanning %}.{%- endif %}
|
||||
| `secret_scanning_push_protection_disable` | Triggered when an organization owner or person with admin access to the organization disables push protection for {% data variables.product.prodname_secret_scanning %}. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
| `secret_scanning_push_protection_enable` | Triggered when an organization owner or person with admin access to the organization enables push protection for {% data variables.product.prodname_secret_scanning %}.{%- endif %}
|
||||
| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
|
||||
| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% ifversion fpt or ghes or ghec %}
|
||||
| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %}
|
||||
|
|
@ -457,20 +457,20 @@ For more information, see "[AUTOTITLE](/organizations/managing-organization-sett
|
|||
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
| `create ` | Triggered when branch protection is enabled on a branch.
|
||||
| `create` | Triggered when branch protection is enabled on a branch.
|
||||
| `destroy` | Triggered when branch protection is disabled on a branch.
|
||||
| `update_admin_enforced ` | Triggered when branch protection is enforced for repository administrators.
|
||||
| `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch.
|
||||
| `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch.
|
||||
| `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch.
|
||||
| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
|
||||
| `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch.
|
||||
| `update_admin_enforced` | Triggered when branch protection is enforced for repository administrators.
|
||||
| `update_require_code_owner_review` | Triggered when enforcement of required Code Owner review is updated on a branch.
|
||||
| `dismiss_stale_reviews` | Triggered when enforcement of dismissing stale pull requests is updated on a branch.
|
||||
| `update_signature_requirement_enforcement_level` | Triggered when enforcement of required commit signing is updated on a branch.
|
||||
| `update_pull_request_reviews_enforcement_level` | Triggered when enforcement of required pull request reviews is updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
|
||||
| `update_required_status_checks_enforcement_level` | Triggered when enforcement of required status checks is updated on a branch.
|
||||
| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed.
|
||||
| `rejected_ref_update ` | Triggered when a branch update attempt is rejected.
|
||||
| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.
|
||||
| `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch.
|
||||
| `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch.
|
||||
| `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch.
|
||||
| `rejected_ref_update` | Triggered when a branch update attempt is rejected.
|
||||
| `policy_override` | Triggered when a branch protection requirement is overridden by a repository administrator.
|
||||
| `update_allow_force_pushes_enforcement_level` | Triggered when force pushes are enabled or disabled for a protected branch.
|
||||
| `update_allow_deletions_enforcement_level` | Triggered when branch deletion is enabled or disabled for a protected branch.
|
||||
| `update_linear_history_requirement_enforcement_level` | Triggered when required linear commit history is enabled or disabled for a protected branch.
|
||||
|
||||
## `pull_request` category actions
|
||||
|
||||
|
|
|
|||
|
|
@ -306,7 +306,7 @@ This qualifier takes a date as its parameter. {% data reusables.time_date.date_f
|
|||
| Qualifier | Example
|
||||
| ------------- | -------------
|
||||
| <code>closed:><em>YYYY-MM-DD</em></code> | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) matches issues and pull requests in Swift that were closed after June 11, 2014.
|
||||
| `in:body `<code>closed:<<em>YYYY-MM-DD</em></code> | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) matches issues and pull requests with the word "data" in the body that were closed before October 2012.
|
||||
| <code>in:body closed:<<em>YYYY-MM-DD</em></code> | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) matches issues and pull requests with the word "data" in the body that were closed before October 2012.
|
||||
|
||||
## Search by when a pull request was merged
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
1. Download the upgrade package to {% data variables.location.product_location %} using `curl `:
|
||||
1. Download the upgrade package to {% data variables.location.product_location %} using `curl`:
|
||||
```shell
|
||||
admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL
|
||||
```
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче