зеркало из https://github.com/github/docs.git
Merge branch 'main' into patch-2
This commit is contained in:
Courtney Wilson
GitHub
Коммит
55e15eb838
|
|
@ -35,7 +35,7 @@ In the left sidebar of your dashboard, you can access the top repositories and t
|
|||
|
||||
|
||||
|
||||
The list of top repositories is automatically generated, and can include any repository you have interacted with, whether it's owned directly by your account or not. Interactions include making commits and opening or commenting on issues and pull requests. The list of top repositories cannot be edited, but repositories will drop off the list 4 months after you last interacted with them.
|
||||
The list of top repositories is automatically generated, and can include any repository you have interacted with, whether it's owned directly by your account or not. Interactions include making commits and opening or commenting on issues and pull requests. The list of top repositories cannot be edited, but repositories will drop off the list {% ifversion ghes < 3.6 or ghae < 3.6 %}4 months{% else %}1 year{% endif %} after you last interacted with them.
|
||||
|
||||
You can also find a list of your recently visited repositories, teams, and project boards when you click into the search bar at the top of any page on {% data variables.product.product_name %}.
|
||||
|
||||
|
|
|
|||
|
|
@ -157,7 +157,7 @@ runs:
|
|||
main: 'main.js'
|
||||
```
|
||||
|
||||
### `runs.using`
|
||||
### `runs.using` for JavaScript actions
|
||||
|
||||
**Required** The runtime used to execute the code specified in [`main`](#runsmain).
|
||||
|
||||
|
|
@ -225,7 +225,7 @@ For example, this `cleanup.js` will only run on Linux-based runners:
|
|||
|
||||
**Required** Configures the path to the composite action.
|
||||
|
||||
### `runs.using`
|
||||
### `runs.using` for composite actions
|
||||
|
||||
**Required** You must set this value to `'composite'`.
|
||||
|
||||
|
|
@ -387,7 +387,7 @@ runs:
|
|||
image: 'docker://debian:stretch-slim'
|
||||
```
|
||||
|
||||
### `runs.using`
|
||||
### `runs.using` for Docker container actions
|
||||
|
||||
**Required** You must set this value to `'docker'`.
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ defaultPlatform: linux
|
|||
|
||||
{% note %}
|
||||
|
||||
**Note:** You must add a runner to {% data variables.product.product_name %} before you can configure the self-hosted runner application as a service.
|
||||
**Note:** You must add a runner to {% data variables.product.product_name %} before you can configure the self-hosted runner application as a service.
|
||||
For more information, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)."
|
||||
|
||||
{% endnote %}
|
||||
|
|
@ -177,7 +177,6 @@ Stop-Service "{{ service_win_name }}"
|
|||
```
|
||||
{% endmac %}
|
||||
|
||||
|
||||
{% linux %}
|
||||
|
||||
## Customizing the self-hosted runner service
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ These commands also include configuration arguments, explained below in more det
|
|||
|
||||
### `prepare_job`
|
||||
|
||||
The `prepare_job` command is called when a job is started. {% data variables.product.prodname_actions %} passes in any job or service containers the job has. This command will be called if you have any service or job containers in the job.
|
||||
The `prepare_job` command is called when a job is started. {% data variables.product.prodname_actions %} passes in any job or service containers the job has. This command will be called if you have any service or job containers in the job.
|
||||
|
||||
{% data variables.product.prodname_actions %} assumes that you will do the following tasks in the `prepare_job` command:
|
||||
|
||||
|
|
@ -47,11 +47,11 @@ The `prepare_job` command is called when a job is started. {% data variables.pro
|
|||
- Start the job container.
|
||||
- Start the service containers.
|
||||
- Write to the response file any information that {% data variables.product.prodname_actions %} will need:
|
||||
- Required: State whether the container is an `alpine` linux container (using the `isAlpine` boolean).
|
||||
- Required: State whether the container is an `alpine` linux container (using the `isAlpine` boolean).
|
||||
- Optional: Any context fields you want to set on the job context, otherwise they will be unavailable for users to use. For more information, see "[`job` context](/actions/learn-github-actions/contexts#job-context)."
|
||||
- Return `0` when the health checks have succeeded and the job/service containers are started.
|
||||
|
||||
#### Arguments
|
||||
#### Arguments for `prepare_job`
|
||||
|
||||
- `jobContainer`: **Optional**. An object containing information about the specified job container.
|
||||
- `image`: **Required**. A string containing the Docker image.
|
||||
|
|
@ -86,7 +86,7 @@ The `prepare_job` command is called when a job is started. {% data variables.pro
|
|||
- `serverUrl`: **Optional**. The registry URL.
|
||||
- `portMappings`: **Optional**. A key value hash of _source:target_ ports to map into the container.
|
||||
|
||||
#### Example input
|
||||
#### Example input for `prepare_job`
|
||||
|
||||
```json{:copy}
|
||||
{
|
||||
|
|
@ -171,7 +171,7 @@ The `prepare_job` command is called when a job is started. {% data variables.pro
|
|||
}
|
||||
```
|
||||
|
||||
#### Example output
|
||||
#### Example output for `prepare_job`
|
||||
|
||||
This example output is the contents of the `responseFile` defined in the input above.
|
||||
|
||||
|
|
@ -213,11 +213,11 @@ The `cleanup_job` command is called at the end of a job. {% data variables.produ
|
|||
- Delete the network (if one exists).
|
||||
- Cleanup anything else that was created for the job.
|
||||
|
||||
#### Arguments
|
||||
#### Arguments for `cleanup_job`
|
||||
|
||||
No arguments are provided for `cleanup_job`.
|
||||
|
||||
#### Example input
|
||||
#### Example input for `cleanup_job`
|
||||
|
||||
```json{:copy}
|
||||
{
|
||||
|
|
@ -234,7 +234,7 @@ No arguments are provided for `cleanup_job`.
|
|||
}
|
||||
```
|
||||
|
||||
#### Example output
|
||||
#### Example output for `cleanup_job`
|
||||
|
||||
No output is expected for `cleanup_job`.
|
||||
|
||||
|
|
@ -247,7 +247,7 @@ The `run_container_step` command is called once for each container action in you
|
|||
- Stream any step logs output to stdout and stderr.
|
||||
- Cleanup the container after it executes.
|
||||
|
||||
#### Arguments
|
||||
#### Arguments for `run_container_step`
|
||||
|
||||
- `image`: **Optional**. A string containing the docker image. Otherwise a dockerfile must be provided.
|
||||
- `dockerfile`: **Optional**. A string containing the path to the dockerfile, otherwise an image must be provided.
|
||||
|
|
@ -423,7 +423,7 @@ If your container is defined by a Dockerfile, this example demonstrates how to s
|
|||
}
|
||||
```
|
||||
|
||||
#### Example output
|
||||
#### Example output for `run_container_step`
|
||||
|
||||
No output is expected for `run_container_step`.
|
||||
|
||||
|
|
@ -434,7 +434,7 @@ No output is expected for `run_container_step`.
|
|||
- Invoke the provided script inside the job container and return the exit code.
|
||||
- Stream any step log output to stdout and stderr.
|
||||
|
||||
#### Arguments
|
||||
#### Arguments for `run_script_step`
|
||||
|
||||
- `entryPointArgs`: **Optional**. A list containing the entry point arguments.
|
||||
- `entryPoint`: **Optional**. The container entry point to use if the default image entrypoint should be overwritten.
|
||||
|
|
@ -442,7 +442,7 @@ No output is expected for `run_container_step`.
|
|||
- `workingDirectory`: **Required**. A string containing the absolute path of the working directory.
|
||||
- `environmentVariables`: **Optional**. Sets a map of key environment variables.
|
||||
|
||||
#### Example input
|
||||
#### Example input for `run_script_step`
|
||||
|
||||
```json{:copy}
|
||||
{
|
||||
|
|
@ -467,13 +467,13 @@ No output is expected for `run_container_step`.
|
|||
}
|
||||
```
|
||||
|
||||
#### Example output
|
||||
#### Example output for `run_script_step`
|
||||
|
||||
No output is expected for `run_script_step`.
|
||||
|
||||
## Generating the customization script
|
||||
|
||||
{% data variables.product.prodname_dotcom %} has created an example repository that demonstrates how to generate customization scripts for Docker and Kubernetes.
|
||||
{% data variables.product.prodname_dotcom %} has created an example repository that demonstrates how to generate customization scripts for Docker and Kubernetes.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ As part of an expression, you can use `boolean`, `null`, `number`, or `string` d
|
|||
| `number` | Any number format supported by JSON. |
|
||||
| `string` | You don't need to enclose strings in `{% raw %}${{{% endraw %}` and `{% raw %}}}{% endraw %}`. However, if you do, you must use single quotes (`'`) around the string. To use a literal single quote, escape the literal single quote using an additional single quote (`''`). Wrapping with double quotes (`"`) will throw an error. |
|
||||
|
||||
### Example
|
||||
### Example of literals
|
||||
|
||||
{% raw %}
|
||||
|
||||
|
|
@ -147,7 +147,7 @@ For example, `contains(fromJSON('["push", "pull_request"]'), github.event_name)`
|
|||
|
||||
Returns `true` when `searchString` starts with `searchValue`. This function is not case sensitive. Casts values to a string.
|
||||
|
||||
#### Example
|
||||
#### Example of `startsWith`
|
||||
|
||||
`startsWith('Hello world', 'He')` returns `true`.
|
||||
|
||||
|
|
@ -157,7 +157,7 @@ Returns `true` when `searchString` starts with `searchValue`. This function is n
|
|||
|
||||
Returns `true` if `searchString` ends with `searchValue`. This function is not case sensitive. Casts values to a string.
|
||||
|
||||
#### Example
|
||||
#### Example of `endsWith`
|
||||
|
||||
`endsWith('Hello world', 'ld')` returns `true`.
|
||||
|
||||
|
|
@ -167,7 +167,7 @@ Returns `true` if `searchString` ends with `searchValue`. This function is not c
|
|||
|
||||
Replaces values in the `string`, with the variable `replaceValueN`. Variables in the `string` are specified using the `{N}` syntax, where `N` is an integer. You must specify at least one `replaceValue` and `string`. There is no maximum for the number of variables (`replaceValueN`) you can use. Escape curly braces using double braces.
|
||||
|
||||
#### Example
|
||||
#### Example of `format`
|
||||
|
||||
{% raw %}
|
||||
```js
|
||||
|
|
@ -193,7 +193,7 @@ Returns '{Hello Mona the Octocat!}'.
|
|||
|
||||
The value for `array` can be an array or a string. All values in `array` are concatenated into a string. If you provide `optionalSeparator`, it is inserted between the concatenated values. Otherwise, the default separator `,` is used. Casts values to a string.
|
||||
|
||||
#### Example
|
||||
#### Example of `join`
|
||||
|
||||
`join(github.event.issue.labels.*.name, ', ')` may return 'bug, help wanted'
|
||||
|
||||
|
|
@ -203,7 +203,7 @@ The value for `array` can be an array or a string. All values in `array` are con
|
|||
|
||||
Returns a pretty-print JSON representation of `value`. You can use this function to debug the information provided in contexts.
|
||||
|
||||
#### Example
|
||||
#### Example of `toJSON`
|
||||
|
||||
`toJSON(job)` might return `{ "status": "Success" }`
|
||||
|
||||
|
|
@ -297,7 +297,7 @@ You can use the following status check functions as expressions in `if` conditio
|
|||
|
||||
Returns `true` when none of the previous steps have failed or been canceled.
|
||||
|
||||
#### Example
|
||||
#### Example of `success`
|
||||
|
||||
```yaml
|
||||
steps:
|
||||
|
|
@ -310,7 +310,7 @@ steps:
|
|||
|
||||
Causes the step to always execute, and returns `true`, even when canceled. A job or step will not run when a critical failure prevents the task from running. For example, if getting sources failed.
|
||||
|
||||
#### Example
|
||||
#### Example of `always`
|
||||
|
||||
```yaml
|
||||
if: {% raw %}${{ always() }}{% endraw %}
|
||||
|
|
@ -320,7 +320,7 @@ if: {% raw %}${{ always() }}{% endraw %}
|
|||
|
||||
Returns `true` if the workflow was canceled.
|
||||
|
||||
#### Example
|
||||
#### Example of `cancelled`
|
||||
|
||||
```yaml
|
||||
if: {% raw %}${{ cancelled() }}{% endraw %}
|
||||
|
|
@ -330,7 +330,7 @@ if: {% raw %}${{ cancelled() }}{% endraw %}
|
|||
|
||||
Returns `true` when any previous step of a job fails. If you have a chain of dependent jobs, `failure()` returns `true` if any ancestor job fails.
|
||||
|
||||
#### Example
|
||||
#### Example of `failure`
|
||||
|
||||
```yaml
|
||||
steps:
|
||||
|
|
@ -343,7 +343,7 @@ steps:
|
|||
|
||||
You can include extra conditions for a step to run after a failure, but you must still include `failure()` to override the default status check of `success()` that is automatically applied to `if` conditions that don't contain a status check function.
|
||||
|
||||
##### Example
|
||||
##### Example of `failure` with conditions
|
||||
|
||||
```yaml
|
||||
steps:
|
||||
|
|
|
|||
|
|
@ -91,7 +91,7 @@ jobs:
|
|||
POSTGRES_PORT: 5432
|
||||
```
|
||||
|
||||
### Configuring the runner job
|
||||
### Configuring the runner job for jobs in containers
|
||||
|
||||
{% data reusables.actions.service-container-host %}
|
||||
|
||||
|
|
@ -123,7 +123,7 @@ jobs:
|
|||
--health-retries 5
|
||||
```
|
||||
|
||||
### Configuring the steps
|
||||
### Configuring the steps for jobs in containers
|
||||
|
||||
{% data reusables.actions.service-template-steps %}
|
||||
|
||||
|
|
@ -213,7 +213,7 @@ jobs:
|
|||
POSTGRES_PORT: 5432
|
||||
```
|
||||
|
||||
### Configuring the runner job
|
||||
### Configuring the runner job for jobs directly on the runner machine
|
||||
|
||||
{% data reusables.actions.service-container-host-runner %}
|
||||
|
||||
|
|
@ -248,7 +248,7 @@ jobs:
|
|||
- 5432:5432
|
||||
```
|
||||
|
||||
### Configuring the steps
|
||||
### Configuring the steps for jobs directly on the runner machine
|
||||
|
||||
{% data reusables.actions.service-template-steps %}
|
||||
|
||||
|
|
|
|||
|
|
@ -117,7 +117,7 @@ jobs:
|
|||
--health-retries 5
|
||||
```
|
||||
|
||||
### Configuring the steps
|
||||
### Configuring the steps for the container job
|
||||
|
||||
{% data reusables.actions.service-template-steps %}
|
||||
|
||||
|
|
@ -235,7 +235,7 @@ jobs:
|
|||
- 6379:6379
|
||||
```
|
||||
|
||||
### Configuring the steps
|
||||
### Configuring the steps for the runner job
|
||||
|
||||
{% data reusables.actions.service-template-steps %}
|
||||
|
||||
|
|
@ -283,7 +283,7 @@ const redis = require("redis");
|
|||
// If REDIS_PORT is not set, the default port is 6379
|
||||
const redisClient = redis.createClient({
|
||||
host: process.env.REDIS_HOST,
|
||||
port: process.env.REDIS_PORT
|
||||
port: process.env.REDIS_PORT
|
||||
});
|
||||
|
||||
redisClient.on("error", function(err) {
|
||||
|
|
@ -319,7 +319,7 @@ When you run this workflow, you should see the following output in the "Connect
|
|||
Reply: OK
|
||||
Reply: 1
|
||||
Reply: 1
|
||||
Reply: 1
|
||||
Reply: 1
|
||||
3 replies:
|
||||
0: octocat
|
||||
1: dinotocat
|
||||
|
|
|
|||
|
|
@ -20,3 +20,7 @@ miniTocMaxHeadingLevel: 4
|
|||
## Assigning permissions to a specific job
|
||||
|
||||
{% data reusables.actions.jobs.section-assigning-permissions-to-jobs-specific %}
|
||||
|
||||
### Example: Setting permissions for a specific job
|
||||
|
||||
{% data reusables.actions.jobs.setting-permissions-specific-jobs-example %}
|
||||
|
|
|
|||
|
|
@ -28,3 +28,7 @@ miniTocMaxHeadingLevel: 4
|
|||
## Setting default shell and working directory for a job
|
||||
|
||||
{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults-job-run %}
|
||||
|
||||
### Example: Setting default `run` step options for a job
|
||||
|
||||
{% data reusables.actions.jobs.setting-default-run-value-for-job-example %}
|
||||
|
|
|
|||
|
|
@ -626,7 +626,7 @@ jobs:
|
|||
- run: echo 'A review from octo-team was requested'
|
||||
```
|
||||
|
||||
#### Running your workflow based on the head or base branch of a pull request
|
||||
#### Running your `pull_request` workflow based on the head or base branch of a pull request
|
||||
|
||||
You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)."
|
||||
|
||||
|
|
@ -673,7 +673,7 @@ jobs:
|
|||
- run: echo "The head of this PR starts with 'releases/'"
|
||||
```
|
||||
|
||||
#### Running your workflow based on files changed in a pull request
|
||||
#### Running your `pull_request` workflow based on files changed in a pull request
|
||||
|
||||
You can also configure your workflow to run when a pull request changes specific files. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
|
||||
|
||||
|
|
@ -703,7 +703,7 @@ on:
|
|||
|
||||
{% endnote %}
|
||||
|
||||
#### Running your workflow when a pull request merges
|
||||
#### Running your `pull_request` workflow when a pull request merges
|
||||
|
||||
When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged.
|
||||
|
||||
|
|
@ -825,7 +825,7 @@ on:
|
|||
types: [assigned, opened, synchronize, reopened]
|
||||
```
|
||||
|
||||
#### Running your workflow based on the head or base branch of a pull request
|
||||
#### Running your `pull_request_target` workflow based on the head or base branch of a pull request
|
||||
|
||||
You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)."
|
||||
|
||||
|
|
@ -872,7 +872,7 @@ jobs:
|
|||
- run: echo "The head of this PR starts with 'releases/'"
|
||||
```
|
||||
|
||||
#### Running your workflow based on files changed in a pull request
|
||||
#### Running your `pull_request_target` workflow based on files changed in a pull request
|
||||
|
||||
You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a pull request changes specific files. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
|
||||
|
||||
|
|
@ -902,7 +902,7 @@ on:
|
|||
|
||||
{% endnote %}
|
||||
|
||||
#### Running your workflow when a pull request merges
|
||||
#### Running your `pull_request_target` workflow when a pull request merges
|
||||
|
||||
When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request_target` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged.
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ Actions can communicate with the runner machine to set environment variables, ou
|
|||
|
||||
Most workflow commands use the `echo` command in a specific format, while others are invoked by writing to a file. For more information, see "[Environment files](#environment-files)."
|
||||
|
||||
### Example
|
||||
### Example of a workflow command
|
||||
|
||||
{% bash %}
|
||||
|
||||
|
|
@ -540,7 +540,7 @@ The example above prints the following lines to the log:
|
|||
```
|
||||
|
||||
Only the second `set-output` and `echo` workflow commands are included in the log because command echoing was only enabled when they were run. Even though it is not always echoed, the output parameter is set in all cases.
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Sending values to the pre and post actions
|
||||
|
|
@ -643,7 +643,7 @@ echo "{environment_variable_name}={value}" >> $GITHUB_ENV
|
|||
|
||||
You can make an environment variable available to any subsequent steps in a workflow job by defining or updating the environment variable and writing this to the `GITHUB_ENV` environment file. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. The names of environment variables are case-sensitive, and you can include punctuation. For more information, see "[Environment variables](/actions/learn-github-actions/environment-variables)."
|
||||
|
||||
### Example
|
||||
### Example of writing an environment variable to `GITHUB_ENV`
|
||||
|
||||
{% bash %}
|
||||
|
||||
|
|
@ -697,7 +697,7 @@ For multiline strings, you may use a delimiter with the following syntax.
|
|||
|
||||
{% endwarning %}
|
||||
|
||||
#### Example
|
||||
#### Example of a multiline string
|
||||
|
||||
This example uses `EOF` as a delimiter, and sets the `JSON_RESPONSE` environment variable to the value of the `curl` response.
|
||||
|
||||
|
|
@ -750,7 +750,7 @@ echo "{name}={value}" >> $GITHUB_OUTPUT
|
|||
|
||||
{% endpowershell %}
|
||||
|
||||
### Example
|
||||
### Example of setting an output parameter
|
||||
|
||||
{% bash %}
|
||||
|
||||
|
|
@ -812,7 +812,7 @@ Job summaries support [{% data variables.product.prodname_dotcom %} flavored Mar
|
|||
|
||||
When a job finishes, the summaries for all steps in a job are grouped together into a single job summary and are shown on the workflow run summary page. If multiple jobs generate summaries, the job summaries are ordered by job completion time.
|
||||
|
||||
### Example
|
||||
### Example of adding a job summary
|
||||
|
||||
{% bash %}
|
||||
|
||||
|
|
@ -836,7 +836,7 @@ echo "### Hello world! :rocket:" >> $GITHUB_STEP_SUMMARY
|
|||
|
||||
For multiline Markdown content, you can use `>>` to continuously append content for the current step. With every append operation, a newline character is automatically added.
|
||||
|
||||
#### Example
|
||||
#### Example of multiline Markdown content
|
||||
|
||||
{% bash %}
|
||||
|
||||
|
|
@ -870,7 +870,7 @@ For multiline Markdown content, you can use `>>` to continuously append content
|
|||
|
||||
To clear all content for the current step, you can use `>` to overwrite any previously added content.
|
||||
|
||||
#### Example
|
||||
#### Example of overwriting job summaries
|
||||
|
||||
{% bash %}
|
||||
|
||||
|
|
@ -898,7 +898,7 @@ To clear all content for the current step, you can use `>` to overwrite any prev
|
|||
|
||||
To completely remove a summary for the current step, the file that `GITHUB_STEP_SUMMARY` references can be deleted.
|
||||
|
||||
#### Example
|
||||
#### Example of removing job summaries
|
||||
|
||||
{% bash %}
|
||||
|
||||
|
|
@ -949,7 +949,7 @@ echo "{path}" >> $GITHUB_PATH
|
|||
|
||||
{% endpowershell %}
|
||||
|
||||
### Example
|
||||
### Example of adding a system path
|
||||
|
||||
{% bash %}
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ The name for workflow runs generated from the workflow. {% data variables.produc
|
|||
|
||||
This value can include expressions and can reference the [`github`](/actions/learn-github-actions/contexts#github-context) and [`inputs`](/actions/learn-github-actions/contexts#inputs-context) contexts.
|
||||
|
||||
### Example
|
||||
### Example of `run-name`
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
|
@ -88,7 +88,7 @@ Within the called workflow, you can use the `inputs` context to refer to an inpu
|
|||
|
||||
If a caller workflow passes an input that is not specified in the called workflow, this results in an error.
|
||||
|
||||
#### Example
|
||||
#### Example of `on.workflow_call.inputs`
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
|
@ -123,7 +123,7 @@ A map of outputs for a called workflow. Called workflow outputs are available to
|
|||
|
||||
In the example below, two outputs are defined for this reusable workflow: `workflow_output1` and `workflow_output2`. These are mapped to outputs called `job_output1` and `job_output2`, both from a job called `my_job`.
|
||||
|
||||
#### Example
|
||||
#### Example of `on.workflow_call.outputs`
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
|
@ -156,7 +156,7 @@ Within the called workflow, you can use the `secrets` context to refer to a secr
|
|||
|
||||
If a caller workflow passes a secret that is not specified in the called workflow, this results in an error.
|
||||
|
||||
#### Example
|
||||
#### Example of `on.workflow_call.secrets`
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
|
@ -215,7 +215,7 @@ Variables in the `env` map cannot be defined in terms of other variables in the
|
|||
|
||||
{% data reusables.repositories.actions-env-var-note %}
|
||||
|
||||
### Example
|
||||
### Example of `env`
|
||||
|
||||
```yaml
|
||||
env:
|
||||
|
|
@ -250,6 +250,10 @@ env:
|
|||
|
||||
{% data reusables.actions.jobs.section-assigning-permissions-to-jobs-specific %}
|
||||
|
||||
#### Example: Setting permissions for a specific job
|
||||
|
||||
{% data reusables.actions.jobs.setting-permissions-specific-jobs-example %}
|
||||
|
||||
## `jobs.<job_id>.needs`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-jobs-in-a-workflow-needs %}
|
||||
|
|
@ -280,7 +284,7 @@ A `map` of variables that are available to all steps in the job. You can set var
|
|||
|
||||
{% data reusables.repositories.actions-env-var-note %}
|
||||
|
||||
### Example
|
||||
### Example of `jobs.<job_id>.env`
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
|
|
@ -297,13 +301,17 @@ jobs:
|
|||
|
||||
{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults-job-run %}
|
||||
|
||||
#### Example: Setting default `run` step options for a job
|
||||
|
||||
{% data reusables.actions.jobs.setting-default-run-value-for-job-example %}
|
||||
|
||||
## `jobs.<job_id>.steps`
|
||||
|
||||
A job contains a sequence of tasks called `steps`. Steps can run commands, run setup tasks, or run an action in your repository, a public repository, or an action published in a Docker registry. Not all steps run actions, but all actions run as a step. Each step runs in its own process in the runner environment and has access to the workspace and filesystem. Because steps run in their own process, changes to environment variables are not preserved between steps. {% data variables.product.prodname_dotcom %} provides built-in steps to set up and complete a job.
|
||||
|
||||
You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
|
||||
|
||||
### Example
|
||||
### Example of `jobs.<job_id>.steps`
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
|
@ -667,7 +675,7 @@ For built-in shell keywords, we provide the following defaults that are executed
|
|||
|
||||
A `map` of the input parameters defined by the action. Each input parameter is a key/value pair. Input parameters are set as environment variables. The variable is prefixed with `INPUT_` and converted to upper case.
|
||||
|
||||
#### Example
|
||||
#### Example of `jobs.<job_id>.steps[*].with`
|
||||
|
||||
Defines the three input parameters (`first_name`, `middle_name`, and `last_name`) defined by the `hello_world` action. These input variables will be accessible to the `hello-world` action as `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME`, and `INPUT_LAST_NAME` environment variables.
|
||||
|
||||
|
|
@ -687,7 +695,7 @@ jobs:
|
|||
|
||||
A `string` that defines the inputs for a Docker container. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up. An `array of strings` is not supported by this parameter. A single argument that includes spaces should be surrounded by double quotes `""`.
|
||||
|
||||
#### Example
|
||||
#### Example of `jobs.<job_id>.steps[*].with.args`
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
|
@ -710,7 +718,7 @@ The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you
|
|||
|
||||
Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Unlike the Docker `ENTRYPOINT` instruction which has a shell and exec form, `entrypoint` keyword accepts only a single string defining the executable to be run.
|
||||
|
||||
#### Example
|
||||
#### Example of `jobs.<job_id>.steps[*].with.entrypoint`
|
||||
|
||||
```yaml
|
||||
steps:
|
||||
|
|
@ -730,7 +738,7 @@ Sets variables for steps to use in the runner environment. You can also set vari
|
|||
|
||||
Public actions may specify expected variables in the README file. If you are setting a secret or sensitive value, such as a password or token, you must set secrets using the `secrets` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
|
||||
|
||||
#### Example
|
||||
#### Example of `jobs.<job_id>.steps[*].env`
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
|
@ -900,7 +908,7 @@ The Docker image to use as the service container to run the action. The value ca
|
|||
|
||||
{% data reusables.actions.registry-credentials %}
|
||||
|
||||
#### Example
|
||||
#### Example of `jobs.<job_id>.services.<service_id>.credentials`
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
|
|
@ -936,7 +944,7 @@ To specify a volume, you specify the source and destination path:
|
|||
|
||||
The `<source>` is a volume name or an absolute path on the host machine, and `<destinationPath>` is an absolute path in the container.
|
||||
|
||||
#### Example
|
||||
#### Example of `jobs.<job_id>.services.<service_id>.volumes`
|
||||
|
||||
```yaml
|
||||
volumes:
|
||||
|
|
@ -964,7 +972,7 @@ The location and version of a reusable workflow file to run as a job. {% ifversi
|
|||
|
||||
{% data reusables.actions.reusable-workflow-calling-syntax %}
|
||||
|
||||
### Example
|
||||
### Example of `jobs.<job_id>.uses`
|
||||
|
||||
{% data reusables.actions.uses-keyword-example %}
|
||||
|
||||
|
|
@ -978,7 +986,7 @@ Any inputs that you pass must match the input specifications defined in the call
|
|||
|
||||
Unlike [`jobs.<job_id>.steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs.<job_id>.with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context.
|
||||
|
||||
#### Example
|
||||
#### Example of `jobs.<job_id>.with`
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
|
|
@ -1018,7 +1026,7 @@ jobs:
|
|||
|
||||
Use the `inherit` keyword to pass all the calling workflow's secrets to the called workflow. This includes all secrets the calling workflow has access to, namely organization, repository, and environment secrets. The `inherit` keyword can be used to pass secrets across repositories within the same organization, or across organizations within the same enterprise.
|
||||
|
||||
#### Example
|
||||
#### Example of `jobs.<job_id>.secrets.inherit`
|
||||
|
||||
{% raw %}
|
||||
|
||||
|
|
|
|||
|
|
@ -29,13 +29,13 @@ You can access your resources in {% data variables.product.product_name %} in a
|
|||
|
||||
{% ifversion ghae %}
|
||||
|
||||
You can authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
|
||||
You can authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)."
|
||||
|
||||
{% else %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
If you're not a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also use two-factor authentication and SAML single sign-on, which can be required by organization and enterprise owners.
|
||||
|
||||
|
|
@ -46,15 +46,15 @@ You can authenticate to {% data variables.product.product_name %} in your browse
|
|||
{% endif %}
|
||||
|
||||
- **Username and password only**
|
||||
- You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %}
|
||||
- You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/authentication/keeping-your-account-and-data-secure/creating-a-strong-password)."{% ifversion fpt or ghec %}
|
||||
- If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer.
|
||||
|
||||
After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %}
|
||||
- **Two-factor authentication (2FA)** (recommended)
|
||||
- If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS).{% endif %}{% ifversion 2fa-check-up-period %}
|
||||
- After you configure 2FA, your account enters a check up period for 28 days. You can leave the check up period by successfully performing 2FA within those 28 days. If you don't perform 2FA in that timespan, you'll then be asked to perform 2FA inside one of your existing {% data variables.product.prodname_dotcom_the_website %} sessions.
|
||||
- If you cannot perform 2FA to pass the 28th day checkup, you will be provided a shortcut that lets you reconfigure your 2FA settings. You must reconfigure your settings before you can access the rest of {% data variables.product.prodname_dotcom %}{% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website){% ifversion 2fa-check-up-period %}" and "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication){% endif %}."
|
||||
- In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
|
||||
- If you cannot perform 2FA to pass the 28th day checkup, you will be provided a shortcut that lets you reconfigure your 2FA settings. You must reconfigure your settings before you can access the rest of {% data variables.product.prodname_dotcom %}{% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website){% ifversion 2fa-check-up-period %}" and "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication){% endif %}."
|
||||
- In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
|
@ -72,22 +72,22 @@ You can authenticate to {% data variables.product.product_name %} in your browse
|
|||
{% endif %}
|
||||
|
||||
## Authenticating with {% data variables.product.prodname_desktop %}
|
||||
You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)."
|
||||
You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github)."
|
||||
|
||||
## Authenticating with the API
|
||||
|
||||
You can authenticate with the API in different ways.
|
||||
|
||||
- **{% data variables.product.pat_generic_caps %}s**
|
||||
- In limited situations, such as testing, you can use a {% data variables.product.pat_generic %} to access the API. Using a {% data variables.product.pat_generic %} enables you to revoke access at any time. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
- In limited situations, such as testing, you can use a {% data variables.product.pat_generic %} to access the API. Using a {% data variables.product.pat_generic %} enables you to revoke access at any time. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
- **Web application flow**
|
||||
- For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)."
|
||||
- For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#web-application-flow)."
|
||||
- **GitHub Apps**
|
||||
- For GitHub Apps in production, you should authenticate on behalf of the app installation. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)."
|
||||
- For GitHub Apps in production, you should authenticate on behalf of the app installation. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps)."
|
||||
|
||||
## Authenticating with the command line
|
||||
|
||||
You can access repositories on {% data variables.product.product_name %} from the command line in two ways, HTTPS and SSH, and both have a different way of authenticating. The method of authenticating is determined based on whether you choose an HTTPS or SSH remote URL when you clone the repository. For more information about which way to access, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
|
||||
You can access repositories on {% data variables.product.product_name %} from the command line in two ways, HTTPS and SSH, and both have a different way of authenticating. The method of authenticating is determined based on whether you choose an HTTPS or SSH remote URL when you clone the repository. For more information about which way to access, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)."
|
||||
|
||||
### HTTPS
|
||||
|
||||
|
|
@ -95,7 +95,7 @@ You can work with all repositories on {% data variables.product.product_name %}
|
|||
|
||||
If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a {% data variables.product.pat_generic %} or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
|
||||
|
||||
If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a {% data variables.product.pat_generic %}. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git).
|
||||
If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a {% data variables.product.pat_generic %}. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/get-started/getting-started-with-git/caching-your-github-credentials-in-git).
|
||||
|
||||
### SSH
|
||||
|
||||
|
|
@ -103,7 +103,7 @@ You can work with all repositories on {% data variables.product.product_name %}
|
|||
|
||||
If you authenticate with {% data variables.product.prodname_cli %}, the CLI will find SSH public keys on your machine and will prompt you to select one for upload. If {% data variables.product.prodname_cli %} does not find a SSH public key for upload, it can generate a new SSH public/private keypair and upload the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. Then, you can either authenticate with a {% data variables.product.pat_generic %} or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
|
||||
|
||||
If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent).
|
||||
If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent).
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### Authorizing for SAML single sign-on
|
||||
|
|
@ -116,9 +116,9 @@ To use a {% data variables.product.pat_generic %} or SSH key to access resources
|
|||
|
||||
| Token type | Prefix | More information |
|
||||
| :- | :- | :- |
|
||||
| {% data variables.product.pat_v1_caps %} | `ghp_` | {% ifversion pat-v2 %}"[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token#creating-a-personal-access-token-classic)"{% else %}"[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)"{% endif %} |{% ifversion pat-v2 %}
|
||||
| {% data variables.product.pat_v2_caps %} | `github_pat_` | "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token#creating-a-fine-grained-personal-access-token)" |{% endif %}
|
||||
| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" |
|
||||
| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" |
|
||||
| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" |
|
||||
| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" |
|
||||
| {% data variables.product.pat_v1_caps %} | `ghp_` | {% ifversion pat-v2 %}"[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#creating-a-personal-access-token-classic)"{% else %}"[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)"{% endif %} |{% ifversion pat-v2 %}
|
||||
| {% data variables.product.pat_v2_caps %} | `github_pat_` | "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token#creating-a-fine-grained-personal-access-token)" |{% endif %}
|
||||
| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps/authorizing-oauth-apps)" |
|
||||
| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)" |
|
||||
| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" |
|
||||
| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens)" |
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ topics:
|
|||
shortTitle: GitHub's IP addresses
|
||||
---
|
||||
|
||||
You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)."
|
||||
You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/meta)."
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
@ -37,4 +37,4 @@ For applications to function, you must allow TCP ports 22, 80, 443, and 9418 via
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"
|
||||
- "[Troubleshooting connectivity problems](/get-started/using-github/troubleshooting-connectivity-problems)"
|
||||
|
|
|
|||
|
|
@ -53,4 +53,4 @@ This means that, in order for ExampleApp to create an issue on Alice's behalf, i
|
|||
|
||||
* ExampleApp's {% data variables.product.prodname_github_app %} requests write access to issues.
|
||||
* A user having admin access for Repo A must have installed ExampleApp's {% data variables.product.prodname_github_app %} on Repo A.
|
||||
* Alice must have read permission for Repo A. For information about which permissions are required to perform various activities, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
|
||||
* Alice must have read permission for Repo A. For information about which permissions are required to perform various activities, see "[Repository roles for an organization](/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ When an {% data variables.product.prodname_oauth_app %} wants to identify you by
|
|||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** You must [verify your email address](/articles/verifying-your-email-address) before you can authorize an {% data variables.product.prodname_oauth_app %}.
|
||||
**Tip:** You must [verify your email address](/get-started/signing-up-for-github/verifying-your-email-address) before you can authorize an {% data variables.product.prodname_oauth_app %}.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
|
@ -43,7 +43,7 @@ When an {% data variables.product.prodname_oauth_app %} wants to identify you by
|
|||
|
||||
*Scopes* are named groups of permissions that an {% data variables.product.prodname_oauth_app %} can request to access both public and non-public data.
|
||||
|
||||
When you want to use an {% data variables.product.prodname_oauth_app %} that integrates with {% data variables.product.product_name %}, that app lets you know what type of access to your data will be required. If you grant access to the app, then the app will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
|
||||
When you want to use an {% data variables.product.prodname_oauth_app %} that integrates with {% data variables.product.product_name %}, that app lets you know what type of access to your data will be required. If you grant access to the app, then the app will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps/scopes-for-oauth-apps)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
|
|
@ -62,7 +62,7 @@ When you want to use an {% data variables.product.prodname_oauth_app %} that int
|
|||
| Commit status | You can grant access for an app to report your commit status. Commit status access allows apps to determine if a build is a successful against a specific commit. Apps won't have access to your code, but they can read and write status information against a specific commit. |
|
||||
| Deployments | Deployment status access allows apps to determine if a deployment is successful against a specific commit for public and private repositories. Apps won't have access to your code. |
|
||||
| Gists | [Gist](https://gist.github.com) access allows apps to read or write to both your public and secret Gists. |
|
||||
| Hooks | [Webhooks](/webhooks) access allows apps to read or write hook configurations on repositories you manage. |
|
||||
| Hooks | [Webhooks](/developers/webhooks-and-events/webhooks/about-webhooks) access allows apps to read or write hook configurations on repositories you manage. |
|
||||
| Notifications | Notification access allows apps to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, apps remain unable to access anything in your repositories. |
|
||||
| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. |
|
||||
| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. |
|
||||
|
|
@ -80,7 +80,7 @@ When {% data variables.product.prodname_oauth_apps %} request new access permiss
|
|||
|
||||
When you authorize an {% data variables.product.prodname_oauth_app %} for your personal account, you'll also see how the authorization will affect each organization you're a member of.
|
||||
|
||||
- **For organizations *with* {% data variables.product.prodname_oauth_app %} access restrictions, you can request that organization admins approve the application for use in that organization.** If the organization does not approve the application, then the application will only be able to access the organization's public resources. If you're an organization admin, you can [approve the application](/articles/approving-oauth-apps-for-your-organization) yourself.
|
||||
- **For organizations *with* {% data variables.product.prodname_oauth_app %} access restrictions, you can request that organization admins approve the application for use in that organization.** If the organization does not approve the application, then the application will only be able to access the organization's public resources. If you're an organization admin, you can [approve the application](/organizations/managing-oauth-access-to-your-organizations-data/approving-oauth-apps-for-your-organization) yourself.
|
||||
|
||||
- **For organizations *without* {% data variables.product.prodname_oauth_app %} access restrictions, the application will automatically be authorized for access to that organization's resources.** For this reason, you should be careful about which {% data variables.product.prodname_oauth_apps %} you approve for access to your personal account resources as well as any organization resources.
|
||||
|
||||
|
|
@ -94,8 +94,8 @@ If you belong to any organizations with SAML single sign-on (SSO) enabled, and y
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
|
||||
- "[Authorizing GitHub Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)"
|
||||
- "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)"
|
||||
- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/organizations/managing-oauth-access-to-your-organizations-data/about-oauth-app-access-restrictions)"
|
||||
- "[Authorizing GitHub Apps](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)"
|
||||
- "[{% data variables.product.prodname_marketplace %} support](/support/learning-about-github-support/github-marketplace-support)"
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ Applications can have *read* or *write* access to your {% data variables.product
|
|||
|
||||
*Scopes* are named groups of permissions that an application can request to access both public and non-public data.
|
||||
|
||||
When you want to use a third-party application that integrates with {% data variables.product.product_name %}, that application lets you know what type of access to your data will be required. If you grant access to the application, then the application will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
|
||||
When you want to use a third-party application that integrates with {% data variables.product.product_name %}, that application lets you know what type of access to your data will be required. If you grant access to the application, then the application will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps/scopes-for-oauth-apps)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
|
|
@ -63,7 +63,7 @@ There are several types of data that applications can request.
|
|||
| Commit status | You can grant access for a third-party application to report your commit status. Commit status access allows applications to determine if a build is a successful against a specific commit. Applications won't have access to your code, but they <em>can</em> read and write status information against a specific commit. |
|
||||
| Deployments | Deployment status access allows applications to determine if a deployment is successful against a specific commit for a repository. Applications won't have access to your code. |
|
||||
| Gists | [Gist](https://gist.github.com) access allows applications to read or write to {% ifversion not ghae %}both your public and{% else %}both your internal and{% endif %} secret Gists. |
|
||||
| Hooks | [Webhooks](/webhooks) access allows applications to read or write hook configurations on repositories you manage. |
|
||||
| Hooks | [Webhooks](/developers/webhooks-and-events/webhooks/about-webhooks) access allows applications to read or write hook configurations on repositories you manage. |
|
||||
| Notifications | Notification access allows applications to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, applications remain unable to access anything in your repositories. |
|
||||
| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. |
|
||||
| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. |
|
||||
|
|
|
|||
|
|
@ -65,7 +65,7 @@ Additionally, organization owners can restrict the access of {% data variables.p
|
|||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
|
||||
{% ifversion fpt or ghec %}1. [Verify your email address](/get-started/signing-up-for-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.developer_settings %}
|
||||
1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Fine-grained tokens**.
|
||||
|
|
@ -106,7 +106,7 @@ If you selected an organization as the resource owner and the organization requi
|
|||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
|
||||
{% ifversion fpt or ghec %}1. [Verify your email address](/get-started/signing-up-for-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.developer_settings %}
|
||||
{% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %}
|
||||
|
|
@ -115,7 +115,7 @@ If you selected an organization as the resource owner and the organization requi
|
|||
|
||||
6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
|
||||
|
||||
7. Select the scopes you'd like to grant this token. To use your token to access repositories from the command line, select **repo**. A token with no assigned scopes can only access public information. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
|
||||
7. Select the scopes you'd like to grant this token. To use your token to access repositories from the command line, select **repo**. A token with no assigned scopes can only access public information. For more information, see "[Available scopes](/developers/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
{% elsif ghae %}
|
||||
|
|
@ -135,13 +135,13 @@ If you selected an organization as the resource owner and the organization requi
|
|||
|
||||
{% data reusables.command_line.providing-token-as-password %}
|
||||
|
||||
{% data variables.product.pat_generic_caps %}s can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to [switch the remote from SSH to HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https).
|
||||
{% data variables.product.pat_generic_caps %}s can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to [switch the remote from SSH to HTTPS](/get-started/getting-started-with-git/managing-remote-repositories#switching-remote-urls-from-ssh-to-https).
|
||||
|
||||
If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token.
|
||||
If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain) to replace your old password with the token.
|
||||
|
||||
Instead of manually entering your {% data variables.product.pat_generic %} for every HTTPS Git operation, you can cache your {% data variables.product.pat_generic %} with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
|
||||
Instead of manually entering your {% data variables.product.pat_generic %} for every HTTPS Git operation, you can cache your {% data variables.product.pat_generic %} with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)."
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"
|
||||
- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"
|
||||
- "[About authentication to GitHub](/authentication/keeping-your-account-and-data-secure/about-authentication-to-github)"
|
||||
- "[Token expiration and revocation](/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation)"
|
||||
|
|
|
|||
|
|
@ -23,16 +23,16 @@ To keep your account secure, we recommend you follow these best practices:
|
|||
- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters.
|
||||
- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
|
||||
|
||||
- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
|
||||
- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)."
|
||||
- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)."
|
||||
- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations)."
|
||||
|
||||
{% data reusables.repositories.blocked-passwords %}
|
||||
|
||||
You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
|
||||
You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/authentication/keeping-your-account-and-data-secure/about-authentication-to-github)."
|
||||
|
||||
{% ifversion fpt or ghec %}{% data reusables.user-settings.password-authentication-deprecation %}{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Caching your {% data variables.product.product_name %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
|
||||
- "[Keeping your account and data secure](/articles/keeping-your-account-and-data-secure/)"
|
||||
- "[Caching your {% data variables.product.product_name %} credentials in Git](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)"
|
||||
- "[Keeping your account and data secure](/authentication/keeping-your-account-and-data-secure)"
|
||||
|
|
|
|||
|
|
@ -18,13 +18,13 @@ shortTitle: Unauthorized access
|
|||
|
||||
After changing your password, you should perform these actions to make sure that your account is secure:
|
||||
|
||||
- [Enable two-factor authentication](/articles/about-two-factor-authentication) on your account so that access requires more than just a password.
|
||||
- [Review your SSH keys](/articles/reviewing-your-ssh-keys), [deploy keys](/articles/reviewing-your-deploy-keys), and [authorized integrations](/articles/reviewing-your-authorized-integrations) and revoke unauthorized or unfamiliar access in your SSH and Applications settings.
|
||||
- [Enable two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication) on your account so that access requires more than just a password.
|
||||
- [Review your SSH keys](/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys), [deploy keys](/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys), and [authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations) and revoke unauthorized or unfamiliar access in your SSH and Applications settings.
|
||||
{% ifversion fpt or ghec %}
|
||||
- [Verify all your email addresses](/articles/verifying-your-email-address). If an attacker added their email address to your account, it could allow them to force an unintended password reset.
|
||||
- [Verify all your email addresses](/get-started/signing-up-for-github/verifying-your-email-address). If an attacker added their email address to your account, it could allow them to force an unintended password reset.
|
||||
{% endif %}
|
||||
- [Review your account's security log](/github/authenticating-to-github/reviewing-your-security-log). This provides an overview on various configurations made to your repositories. For example, you can ensure that no private repositories were turned public, or that no repositories were transferred.
|
||||
- [Review the webhooks](/articles/creating-webhooks) on your repositories. Webhooks could allow an attacker to intercept pushes made to your repository.
|
||||
- [Make sure that no new deploy keys](/guides/managing-deploy-keys/#deploy-keys) were created. This could enable outside servers access to your projects.
|
||||
- [Review your account's security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log). This provides an overview on various configurations made to your repositories. For example, you can ensure that no private repositories were turned public, or that no repositories were transferred.
|
||||
- [Review the webhooks](/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks) on your repositories. Webhooks could allow an attacker to intercept pushes made to your repository.
|
||||
- [Make sure that no new deploy keys](/developers/overview/managing-deploy-keys#deploy-keys) were created. This could enable outside servers access to your projects.
|
||||
- Review recent commits made to your repositories.
|
||||
- Review the list of collaborators for each repository.
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
|
|||
```
|
||||
For more information, see [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) in the `newren/git-filter-repo` repository.
|
||||
|
||||
2. If you don't already have a local copy of your repository with sensitive data in its history, [clone the repository](/articles/cloning-a-repository/) to your local computer.
|
||||
2. If you don't already have a local copy of your repository with sensitive data in its history, [clone the repository](/repositories/creating-and-managing-repositories/cloning-a-repository) to your local computer.
|
||||
```shell
|
||||
$ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY
|
||||
> Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/
|
||||
|
|
@ -139,7 +139,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil
|
|||
> To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME.YOUR-REPOSITORY.git
|
||||
> + 48dc599...051452f main -> main (forced update)
|
||||
```
|
||||
8. In order to remove the sensitive file from [your tagged releases](/articles/about-releases), you'll also need to force-push against your Git tags:
|
||||
8. In order to remove the sensitive file from [your tagged releases](/repositories/releasing-projects-on-github/about-releases), you'll also need to force-push against your Git tags:
|
||||
```shell
|
||||
$ git push origin --force --tags
|
||||
> Counting objects: 321, done.
|
||||
|
|
@ -189,4 +189,4 @@ There are a few simple tricks to avoid committing things you don't want committe
|
|||
|
||||
- [`git filter-repo` man page](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html)
|
||||
- [Pro Git: Git Tools - Rewriting History](https://git-scm.com/book/en/Git-Tools-Rewriting-History)
|
||||
- "[About Secret scanning](/code-security/secret-security/about-secret-scanning)"
|
||||
- "[About Secret scanning](/code-security/secret-scanning/about-secret-scanning)"
|
||||
|
|
|
|||
|
|
@ -22,5 +22,5 @@ shortTitle: Review OAuth apps
|
|||
|
||||
## Further reading
|
||||
{% ifversion fpt or ghec %}
|
||||
- "[About integrations](/articles/about-integrations)"{% endif %}
|
||||
- "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations)"
|
||||
- "[About integrations](/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations)"{% endif %}
|
||||
- "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)"
|
||||
|
|
|
|||
|
|
@ -33,5 +33,5 @@ shortTitle: Authorized integrations
|
|||
|
||||
## Further reading
|
||||
{% ifversion fpt or ghec %}
|
||||
- "[About integrations](/articles/about-integrations)"{% endif %}
|
||||
- "[Reviewing your authorized applications (OAuth)](/articles/reviewing-your-authorized-applications-oauth)"
|
||||
- "[About integrations](/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations)"{% endif %}
|
||||
- "[Reviewing your authorized applications (OAuth)](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)"
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ shortTitle: Deploy keys
|
|||
4. On the Deploy keys page, take note of the deploy keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid deploy keys you'd like to keep, click **Approve**.
|
||||
|
||||
|
||||
For more information, see "[Managing deploy keys](/guides/managing-deploy-keys)."
|
||||
For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys)."
|
||||
|
||||
## Further reading
|
||||
- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
|
||||
|
|
|
|||
|
|
@ -39,19 +39,19 @@ The events listed in your security log are triggered by your actions. Actions ar
|
|||
| Category name | Description
|
||||
|------------------|-------------------{% ifversion fpt or ghec %}
|
||||
| [`billing`](#billing-category-actions) | Contains all activities related to your billing information.
|
||||
| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_github_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)."
|
||||
| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_github_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/codespaces/overview)."
|
||||
| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
|
||||
| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}
|
||||
| [`oauth_access`](#oauth_access-category-actions) | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
|
||||
| [`oauth_access`](#oauth_access-category-actions) | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
|
||||
| [`payment_method`](#payment_method-category-actions) | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %}{% ifversion pat-v2%}
|
||||
| [`personal_access_token`](#personal_access_token-category-actions) | Contains activities related to {% data variables.product.pat_v2 %}s. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."{% endif %}
|
||||
| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your profile picture.
|
||||
| [`project`](#project-category-actions) | Contains all activities related to project boards.
|
||||
| [`public_key`](#public_key-category-actions) | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account).
|
||||
| [`public_key`](#public_key-category-actions) | Contains all activities related to [your public SSH keys](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account).
|
||||
| [`repo`](#repo-category-actions) | Contains all activities related to the repositories you own.{% ifversion fpt or ghec %}
|
||||
| [`sponsors`](#sponsors-category-actions) | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% ifversion ghes or ghae %}
|
||||
| [`sponsors`](#sponsors-category-actions) | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% ifversion ghes or ghae %}
|
||||
| [`team`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% ifversion not ghae %}
|
||||
| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %}
|
||||
| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contains all activities related to [two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa).{% endif %}
|
||||
| [`user`](#user-category-actions) | Contains all activities related to your account.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
|
@ -73,18 +73,18 @@ An overview of some of the most common actions that are recorded as events in th
|
|||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `change_billing_type` | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}.
|
||||
| `change_email` | Triggered when you [change your email address](/articles/changing-your-primary-email-address).
|
||||
| `change_billing_type` | Triggered when you [change how you pay](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}.
|
||||
| `change_email` | Triggered when you [change your email address](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address).
|
||||
|
||||
### `codespaces` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you [create a codespace](/github/developing-online-with-codespaces/creating-a-codespace).
|
||||
| `create` | Triggered when you [create a codespace](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository).
|
||||
| `resume` | Triggered when you resume a suspended codespace.
|
||||
| `delete` | Triggered when you [delete a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).
|
||||
| `manage_access_and_security` | Triggered when you update [the repositories a codespace has access to](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
|
||||
| `trusted_repositories_access_update` | Triggered when you change your personal account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
|
||||
| `delete` | Triggered when you [delete a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace).
|
||||
| `manage_access_and_security` | Triggered when you update [the repositories a codespace has access to](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces).
|
||||
| `trusted_repositories_access_update` | Triggered when you change your personal account's [access and security setting for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces).
|
||||
|
||||
### `marketplace_agreement_signature` category actions
|
||||
|
||||
|
|
@ -108,8 +108,8 @@ An overview of some of the most common actions that are recorded as events in th
|
|||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
|
||||
| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations) and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).
|
||||
| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps).
|
||||
| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations) and when [authorizations are revoked or expire](/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation).
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
|
@ -143,7 +143,7 @@ An overview of some of the most common actions that are recorded as events in th
|
|||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/).
|
||||
| `update` | Triggered when you [set or update your profile picture](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile).
|
||||
|
||||
### `project` category actions
|
||||
|
||||
|
|
@ -162,31 +162,31 @@ An overview of some of the most common actions that are recorded as events in th
|
|||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account).
|
||||
| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).
|
||||
| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account).
|
||||
| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}](/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys).
|
||||
|
||||
### `repo` category actions
|
||||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa).
|
||||
| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[invited to have collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% endif %} to a repository.
|
||||
| `add_topic` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.
|
||||
| `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %}
|
||||
| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
|
||||
| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
|
||||
| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).
|
||||
| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %}
|
||||
| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).
|
||||
| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
|
||||
| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
|
||||
| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility) (or vice versa).
|
||||
| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[invited to have collaboration access](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository){% endif %} to a repository.
|
||||
| `add_topic` | Triggered when a repository owner [adds a topic](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics) to a repository.
|
||||
| `archived` | Triggered when a repository owner [archives a repository](/repositories/archiving-a-github-repository/archiving-repositories).{% ifversion ghes %}
|
||||
| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
|
||||
| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
|
||||
| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise).
|
||||
| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise).{% endif %}
|
||||
| `create` | Triggered when [a new repository is created](/repositories/creating-and-managing-repositories/creating-a-new-repository).
|
||||
| `destroy` | Triggered when [a repository is deleted](/repositories/creating-and-managing-repositories/deleting-a-repository).{% ifversion fpt or ghec %}
|
||||
| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/billing/managing-your-github-billing-settings/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
|
||||
| `download_zip` | Triggered when a ZIP or TAR archive of a repository is downloaded.
|
||||
| `enable` | Triggered when a repository is re-enabled.{% endif %}
|
||||
| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).
|
||||
| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository).
|
||||
| `remove_topic` | Triggered when a repository owner removes a topic from a repository.
|
||||
| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).
|
||||
| `rename` | Triggered when [a repository is renamed](/repositories/creating-and-managing-repositories/renaming-a-repository).
|
||||
| `staff_unlock` | Triggered when an enterprise owner or {% data variables.contact.github_support %} (with permission from a repository administrator) temporarily unlocked the repository. The visibility of the repository isn't changed.
|
||||
| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository).
|
||||
| `transfer` | Triggered when [a repository is transferred](/repositories/creating-and-managing-repositories/transferring-a-repository).
|
||||
| `transfer_start` | Triggered when a repository transfer is about to occur.
|
||||
| `unarchived` | Triggered when a repository owner unarchives a repository.
|
||||
|
||||
|
|
@ -195,13 +195,13 @@ An overview of some of the most common actions that are recorded as events in th
|
|||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `custom_amount_settings_change` | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")
|
||||
| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")
|
||||
| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
|
||||
| `custom_amount_settings_change` | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")
|
||||
| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)")
|
||||
| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)")
|
||||
| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
|
||||
| `sponsor_sponsorship_payment_complete` | Triggered after you sponsor an account and your payment has been processed (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
|
||||
| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")
|
||||
| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
|
||||
| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)")
|
||||
| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")
|
||||
| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")
|
||||
| `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled
|
||||
|
|
@ -219,11 +219,11 @@ An overview of some of the most common actions that are recorded as events in th
|
|||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
|
||||
| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories)")
|
||||
| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories)")
|
||||
| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories)")
|
||||
| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories)")
|
||||
| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories)")
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae %}
|
||||
|
|
@ -232,11 +232,11 @@ An overview of some of the most common actions that are recorded as events in th
|
|||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `add_member` | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team).
|
||||
| `add_member` | Triggered when a member of an organization you belong to [adds you to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team).
|
||||
| `add_repository` | Triggered when a team you are a member of is given control of a repository.
|
||||
| `create` | Triggered when a new team in an organization you belong to is created.
|
||||
| `destroy` | Triggered when a team you are a member of is deleted from the organization.
|
||||
| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of.
|
||||
| `remove_member` | Triggered when a member of an organization is [removed from a team](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team) you are a member of.
|
||||
| `remove_repository` | Triggered when a repository is no longer under a team's control.
|
||||
|
||||
{% endif %}
|
||||
|
|
@ -246,7 +246,7 @@ An overview of some of the most common actions that are recorded as events in th
|
|||
|
||||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `enabled` | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled.
|
||||
| `enabled` | Triggered when [two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa) is enabled.
|
||||
| `disabled` | Triggered when two-factor authentication is disabled.
|
||||
{% endif %}
|
||||
|
||||
|
|
@ -254,25 +254,25 @@ An overview of some of the most common actions that are recorded as events in th
|
|||
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
| `add_email` | Triggered when you {% ifversion not ghae %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %}
|
||||
| `codespaces_trusted_repo_access_granted` | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your personal account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
|
||||
| `codespaces_trusted_repo_access_revoked` | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your personal account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). {% endif %}
|
||||
| `add_email` | Triggered when you {% ifversion not ghae %}[add a new email address](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %}
|
||||
| `codespaces_trusted_repo_access_granted` | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your personal account](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces).
|
||||
| `codespaces_trusted_repo_access_revoked` | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your personal account](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces). {% endif %}
|
||||
| `create` | Triggered when you create a new personal account.{% ifversion not ghae %}
|
||||
| `change_password` | Triggered when you change your password.
|
||||
| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %}
|
||||
| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).
|
||||
| `forgot_password` | Triggered when you ask for [a password reset](/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials).{% endif %}
|
||||
| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile).
|
||||
| `login` | Triggered when you log in to {% data variables.location.product_location %}.{% ifversion ghes or ghae %}
|
||||
`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
|
||||
`mandatory_message_viewed` | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
|
||||
| `failed_login` | Triggered when you failed to log in successfully.
|
||||
| `remove_email` | Triggered when you remove an email address.
|
||||
| `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %}
|
||||
| `report_content` | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %}
|
||||
| `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% ifversion not ghae %}
|
||||
| `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %}
|
||||
| `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile).{% ifversion not ghae %}
|
||||
| `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication).{% endif %}
|
||||
|
||||
### `user_status` category actions
|
||||
|
||||
| Action | Description
|
||||
|--------------------|---------------------
|
||||
| `update` | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)."
|
||||
| `update` | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)."
|
||||
| `destroy` | Triggered when you clear the status on your profile.
|
||||
|
|
|
|||
|
|
@ -20,13 +20,13 @@ This article explains the possible reasons your {% data variables.product.produc
|
|||
|
||||
{% note %}
|
||||
|
||||
**Note:** When a {% data variables.product.pat_generic %} or OAuth token expires or is revoked, you may see an `oauth_authorization.destroy` action in your security log. For more information, see "[Reviewing your security log](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)."
|
||||
**Note:** When a {% data variables.product.pat_generic %} or OAuth token expires or is revoked, you may see an `oauth_authorization.destroy` action in your security log. For more information, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Token revoked after reaching its expiration date
|
||||
|
||||
When you create a {% data variables.product.pat_generic %}, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
When you create a {% data variables.product.pat_generic %}, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Token revoked when pushed to a public repository or public gist
|
||||
|
|
@ -43,13 +43,13 @@ If a valid OAuth token, {% data variables.product.prodname_github_app %} token,
|
|||
|
||||
## Token revoked by the user
|
||||
|
||||
You can revoke your authorization of a {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} from your account settings which will revoke any tokens associated with the app. For more information, see "[Reviewing your authorized integrations](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" and "[Reviewing your authorized applications (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)."
|
||||
You can revoke your authorization of a {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} from your account settings which will revoke any tokens associated with the app. For more information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" and "[Reviewing your authorized applications (OAuth)](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)."
|
||||
|
||||
Once an authorization is revoked, any tokens associated with the authorization will be revoked as well. To re-authorize an application, follow the instructions from the third-party application or website to connect your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} again.
|
||||
|
||||
## Token revoked by the {% data variables.product.prodname_oauth_app %}
|
||||
|
||||
The owner of an {% data variables.product.prodname_oauth_app %} can revoke an account's authorization of their app, this will also revoke any tokens associated with the authorization. For more information about revoking authorizations of your OAuth app, see "[Delete an app authorization](/rest/reference/apps#delete-an-app-authorization)."
|
||||
The owner of an {% data variables.product.prodname_oauth_app %} can revoke an account's authorization of their app, this will also revoke any tokens associated with the authorization. For more information about revoking authorizations of your OAuth app, see "[Delete an app authorization](/rest/apps#delete-an-app-authorization)."
|
||||
|
||||
{% data variables.product.prodname_oauth_app %} owners can also revoke individual tokens associated with an authorization. For more information about revoking individual tokens for your OAuth app, see "[Delete an app token](/rest/apps/oauth-applications#delete-an-app-token)".
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ shortTitle: Update access credentials
|
|||
{% ifversion fpt or ghec %}
|
||||
* If you have set up [{% data variables.product.prodname_mobile %}](https://github.com/mobile), click **Authenticate with GitHub Mobile** instead.
|
||||
{% endif %}
|
||||
5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)."
|
||||
5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/authentication/keeping-your-account-and-data-secure/creating-a-strong-password)."
|
||||
{% ifversion fpt or ghec %}{% else %}
|
||||
{% endif %}
|
||||
|
||||
|
|
@ -54,18 +54,18 @@ To avoid losing your password in the future, we suggest using a secure password
|
|||
1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}.
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.security %}
|
||||
4. Under "Change password", type your old password, a strong new password, and confirm your new password. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)"
|
||||
4. Under "Change password", type your old password, a strong new password, and confirm your new password. For help creating a strong password, see "[Creating a strong password](/authentication/keeping-your-account-and-data-secure/creating-a-strong-password)"
|
||||
5. Click **Update password**.
|
||||
|
||||
{% tip %}
|
||||
|
||||
For greater security, enable two-factor authentication in addition to changing your password. See [About two-factor authentication](/articles/about-two-factor-authentication) for more details.
|
||||
For greater security, enable two-factor authentication in addition to changing your password. See [About two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication) for more details.
|
||||
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
## Updating your access tokens
|
||||
|
||||
See "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations)" for instructions on reviewing and deleting access tokens. To generate new access tokens, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
See "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" for instructions on reviewing and deleting access tokens. To generate new access tokens, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
|
||||
{% ifversion not ghae %}
|
||||
|
||||
|
|
@ -75,14 +75,14 @@ If you have reset your account password and would also like to trigger a sign-ou
|
|||
|
||||
## Updating your SSH keys
|
||||
|
||||
See "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)" for instructions on reviewing and deleting SSH keys. To generate and add new SSH keys, see "[Generating an SSH key](/articles/generating-an-ssh-key)."
|
||||
See "[Reviewing your SSH keys](/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys)" for instructions on reviewing and deleting SSH keys. To generate and add new SSH keys, see "[Generating an SSH key](/authentication/connecting-to-github-with-ssh)."
|
||||
|
||||
## Resetting API tokens
|
||||
|
||||
If you have any applications registered with {% data variables.product.product_name %}, you'll want to reset their OAuth tokens. For more information, see the "[Reset an authorization](/rest/reference/apps#reset-an-authorization)" endpoint.
|
||||
If you have any applications registered with {% data variables.product.product_name %}, you'll want to reset their OAuth tokens. For more information, see the "[Reset an authorization](/rest/apps#reset-an-authorization)" endpoint.
|
||||
|
||||
{% ifversion not ghae %}
|
||||
## Preventing unauthorized access
|
||||
|
||||
For more tips on securing your account and preventing unauthorized access, see "[Preventing unauthorized access](/articles/preventing-unauthorized-access)."
|
||||
For more tips on securing your account and preventing unauthorized access, see "[Preventing unauthorized access](/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access)."
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -31,6 +31,7 @@ includeGuides:
|
|||
- /code-security/secret-scanning/protecting-pushes-with-secret-scanning
|
||||
- /code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection
|
||||
- /code-security/secret-scanning/secret-scanning-patterns
|
||||
- /code-security/secret-scanning/troubleshooting-secret-scanning
|
||||
- /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists
|
||||
- /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
|
||||
- /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts
|
||||
|
|
|
|||
|
|
@ -22,5 +22,6 @@ children:
|
|||
- /secret-scanning-patterns
|
||||
- /protecting-pushes-with-secret-scanning
|
||||
- /pushing-a-branch-blocked-by-push-protection
|
||||
- /troubleshooting-secret-scanning
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -31,6 +31,8 @@ redirect_from:
|
|||
Owners of public repositories, as well as organizations using {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_GH_advanced_security %}, can enable {% data variables.secret-scanning.user_alerts %} on their repositories. For details of these patterns, see the "[Supported secrets for user alerts](#supported-secrets-for-user-alerts) section below.
|
||||
{% endif %}
|
||||
|
||||
If you believe that {% data variables.product.prodname_secret_scanning %} should have detected a secret committed to your repository, and it has not, you first need to check that {% data variables.product.prodname_dotcom %} supports your secret. For more information, refer to the sections below. For more advanced troubleshooting information, see "[Troubleshooting {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/troubleshooting-secret-scanning)."
|
||||
|
||||
## Supported secrets for partner alerts
|
||||
|
||||
{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers and alerts the relevant service provider whenever a secret is detected in a commit. For more information about {% data variables.secret-scanning.partner_alerts %}, see "[About {% data variables.secret-scanning.partner_alerts %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-alerts-for-partners)."
|
||||
|
|
@ -67,6 +69,8 @@ If you use the REST API for secret scanning, you can use the `Secret type` to re
|
|||
|
||||
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-older-tokens %} For more information about push protection limitations, see "[Troubleshooting {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/troubleshooting-secret-scanning#push-protection-and-pattern-versions)."
|
||||
|
||||
{% data reusables.secret-scanning.secret-list-private-push-protection %}
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -0,0 +1,46 @@
|
|||
---
|
||||
title: Troubleshooting secret scanning
|
||||
shortTitle: Troubleshoot secret scanning
|
||||
intro: 'If you have problems with {% data variables.product.prodname_secret_scanning %}, you can use these tips to help resolve issues.'
|
||||
product: '{% data reusables.gated-features.secret-scanning %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Secret scanning
|
||||
- Advanced Security
|
||||
- Troubleshooting
|
||||
---
|
||||
|
||||
{% data reusables.secret-scanning.beta %}
|
||||
{% data reusables.secret-scanning.enterprise-enable-secret-scanning %}
|
||||
|
||||
## Detection of pattern pairs
|
||||
|
||||
{% data variables.product.prodname_secret_scanning_caps %} will only detect pattern pairs, such as AWS Access Keys and Secrets, if the ID and the secret are found in the same file, and both are pushed to the repository. Pair matching helps reduce false positives since both elements of a pair (the ID and the secret) must be used together to access the provider's resource.
|
||||
|
||||
Pairs pushed to different files, or not pushed to the same repository, will not result in alerts. For more information about the supported pattern pairs, see the tables in "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)."
|
||||
|
||||
{% ifversion secret-scanning-validity-check %}
|
||||
## About legacy GitHub tokens
|
||||
|
||||
For {% data variables.product.prodname_dotcom %} tokens, we check the validity of the secret to determine whether the secret is active or inactive. This means that for legacy tokens, {% data variables.product.prodname_secret_scanning %} won't detect a {% data variables.product.prodname_ghe_server %} {% data variables.product.pat_generic %} on {% data variables.product.prodname_ghe_cloud %}. Similarly, a {% data variables.product.prodname_ghe_cloud %} {% data variables.product.pat_generic %} won't be found on {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
{% endif %}
|
||||
{% ifversion secret-scanning-push-protection %}
|
||||
## Push protection limitations
|
||||
|
||||
If push protection did not detect a secret that you think should have been detected, then you should first check that push protection supports the secret type in the list of supported secrets. For further information, see "[Supported secrets for push protection](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-push-protection)."
|
||||
|
||||
If your secret is in the supported list, there are various reasons why push protection may not detect it.
|
||||
|
||||
- Push protection only blocks leaked secrets on a subset of the most identifiable user-alerted patterns. Contributors can trust security defenses when such secrets are blocked as these are the patterns that have the lowest number of false positives.
|
||||
- The version of your secret may be old. {% data reusables.secret-scanning.push-protection-older-tokens %}
|
||||
- The push may be too large, for example, if you're trying to push thousands of large files. A push protection scan may time out and not block a user if the push is too large. {% data variables.product.prodname_dotcom %} will still scan and create alerts, if needed, after the push.
|
||||
- If the push results in the detection of over five new secrets, we will only show you the first five (we will always show you a maximum of five secrets at one time).
|
||||
- If a push contains over 1,000 existing secrets (that is, secrets for which alerts have already been created), push protection will not block the push.
|
||||
|
||||
{% endif %}
|
||||
|
|
@ -47,7 +47,7 @@ For billing purposes, {% data variables.product.prodname_codespaces %} storage i
|
|||
|
||||
## Understanding your {% data variables.product.prodname_codespaces %} usage
|
||||
|
||||
You can check the cumulative {% data variables.product.prodname_github_codespaces %} usage for your current monthly billing cycle in your {% data variables.product.prodname_dotcom %} settings. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](http://127.0.0.1:4000/en/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
You can check the cumulative {% data variables.product.prodname_github_codespaces %} usage for your current monthly billing cycle in your {% data variables.product.prodname_dotcom %} settings. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -60,18 +60,18 @@ When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote reposit
|
|||
{% tip %}
|
||||
|
||||
**Tips**:
|
||||
- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
|
||||
- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
|
||||
- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)."
|
||||
- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %}
|
||||
{% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/authentication/troubleshooting-ssh/using-ssh-over-the-https-port)."{% endif %}
|
||||
|
||||
## Cloning with SSH URLs
|
||||
|
||||
SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)."
|
||||
SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/authentication/connecting-to-github-with-ssh)."
|
||||
|
||||
When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
|
||||
When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases)."
|
||||
|
||||
{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
|
||||
|
||||
|
|
@ -90,7 +90,7 @@ You can also install {% data variables.product.prodname_cli %} to use {% data va
|
|||
|
||||
{% data reusables.subversion.sunset %}
|
||||
|
||||
You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
|
||||
You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/get-started/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git)"
|
||||
|
||||
You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)."
|
||||
You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/get-started/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients)."
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ shortTitle: Caching credentials
|
|||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/articles/generating-an-ssh-key)."
|
||||
**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/authentication/connecting-to-github-with-ssh)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
|
@ -35,7 +35,7 @@ For more information about authenticating with {% data variables.product.prodnam
|
|||
|
||||
## Git Credential Manager
|
||||
|
||||
[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) is another way to store your credentials securely and connect to GitHub over HTTPS. With GCM, you don't have to manually [create and store a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token), as GCM manages authentication on your behalf, including 2FA (two-factor authentication).
|
||||
[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) is another way to store your credentials securely and connect to GitHub over HTTPS. With GCM, you don't have to manually [create and store a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token), as GCM manages authentication on your behalf, including 2FA (two-factor authentication).
|
||||
|
||||
{% mac %}
|
||||
|
||||
|
|
|
|||
|
|
@ -13,4 +13,4 @@ versions:
|
|||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
|
||||
You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)."
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ $ git remote -v
|
|||
> origin https://{% data variables.command_line.codeblock %}/USER/REPO.git (push)
|
||||
```
|
||||
|
||||
For more information on which URL to use, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
|
||||
For more information on which URL to use, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)."
|
||||
|
||||
### Troubleshooting: Remote origin already exists
|
||||
|
||||
|
|
@ -67,7 +67,7 @@ The `git remote set-url` command changes an existing remote repository URL.
|
|||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
|
||||
**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
|
@ -108,7 +108,7 @@ git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git
|
|||
|
||||
The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user-settings.password-authentication-deprecation %}
|
||||
|
||||
You can [use a credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git) so Git will remember your GitHub username and {% data variables.product.pat_generic %} every time it talks to GitHub.
|
||||
You can [use a credential helper](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) so Git will remember your GitHub username and {% data variables.product.pat_generic %} every time it talks to GitHub.
|
||||
|
||||
### Switching remote URLs from HTTPS to SSH
|
||||
|
||||
|
|
@ -153,7 +153,7 @@ The `git remote rename` command takes two arguments:
|
|||
|
||||
## Example
|
||||
|
||||
These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
|
||||
These examples assume you're [cloning using HTTPS](/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls), which is recommended.
|
||||
|
||||
```shell
|
||||
$ git remote -v
|
||||
|
|
@ -198,7 +198,7 @@ Removing the remote URL from your repository only unlinks the local and remote r
|
|||
|
||||
## Example
|
||||
|
||||
These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
|
||||
These examples assume you're [cloning using HTTPS](/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls), which is recommended.
|
||||
|
||||
```shell
|
||||
$ git remote -v
|
||||
|
|
|
|||
|
|
@ -52,5 +52,5 @@ Changing the name associated with your Git commits using `git config` will only
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[Setting your commit email address](/articles/setting-your-commit-email-address)"
|
||||
- "[Setting your commit email address](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address)"
|
||||
- ["Git Configuration" from the _Pro Git_ book](https://git-scm.com/book/en/Customizing-Git-Git-Configuration)
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ shortTitle: macOS Keychain credentials
|
|||
|
||||
**Note:** Updating credentials from the macOS Keychain only applies to users who manually configured a {% data variables.product.pat_generic %} using the `osxkeychain` helper that is built-in to macOS.
|
||||
|
||||
We recommend you either [configure SSH](/articles/generating-an-ssh-key) or upgrade to the [Git Credential Manager](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual {% data variables.product.pat_generic %}s) including 2FA (two-factor auth).
|
||||
We recommend you either [configure SSH](/authentication/connecting-to-github-with-ssh) or upgrade to the [Git Credential Manager](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual {% data variables.product.pat_generic %}s) including 2FA (two-factor auth).
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
|
@ -47,4 +47,4 @@ If it's successful, nothing will print out. To test that it works, try and clone
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
|
||||
- "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/get-started/getting-started-with-git/caching-your-github-credentials-in-git)"
|
||||
|
|
|
|||
|
|
@ -17,10 +17,10 @@ Using an HTTPS remote URL has some advantages compared with using SSH. It's easi
|
|||
|
||||
{% data reusables.user-settings.password-authentication-deprecation %}
|
||||
|
||||
You can avoid being prompted for your password by configuring Git to [cache your credentials](/github/getting-started-with-github/caching-your-github-credentials-in-git) for you. Once you've configured credential caching, Git automatically uses your cached {% data variables.product.pat_generic %} when you pull or push a repository using HTTPS.
|
||||
You can avoid being prompted for your password by configuring Git to [cache your credentials](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) for you. Once you've configured credential caching, Git automatically uses your cached {% data variables.product.pat_generic %} when you pull or push a repository using HTTPS.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
|
||||
- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)"
|
||||
- "[Adding your SSH key to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)"
|
||||
- "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)."
|
||||
- "[About authentication to {% data variables.product.prodname_dotcom %}](/authentication/keeping-your-account-and-data-secure/about-authentication-to-github)"
|
||||
- "[Adding your SSH key to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)"
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ When you open the command palette, it shows your location at the top left and us
|
|||
|
||||
**Notes:**
|
||||
- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).{% ifversion projects-v2 %}
|
||||
- If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."{% endif %}
|
||||
- If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view)."{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
|
@ -219,11 +219,11 @@ These commands are available only when you open the command palette from a pull
|
|||
|
||||
| Command | Behavior|
|
||||
| :- | :- |
|
||||
|`Close`/`reopen pull request`|Close or reopen the current pull request. For more information, see "[About pull requests](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."|
|
||||
|`Convert to draft`/`Mark pull request as ready for review`|Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."|
|
||||
|`Close`/`reopen pull request`|Close or reopen the current pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."|
|
||||
|`Convert to draft`/`Mark pull request as ready for review`|Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."|
|
||||
|`Copy current branch name`| Add the name of the head branch for the pull request to the clipboard.
|
||||
|`Edit pull request body`|Open the main body of the pull request ready for editing.
|
||||
|`Edit pull request title`|Open the title of the pull request ready for editing.
|
||||
|`Open in new codespace`|Create and open a codespace for the head branch of the pull request. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)."
|
||||
|`Subscribe`/`unsubscribe`|Opt in or out of notifications for changes to this pull request. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
|
||||
|`Update current branch`|Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)."|
|
||||
|`Update current branch`|Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)."|
|
||||
|
|
|
|||
|
|
@ -29,9 +29,9 @@ With {% data variables.product.prodname_mobile %} you can:
|
|||
{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication
|
||||
- Verify your sign in attempts on unrecognized devices{% endif %}
|
||||
|
||||
For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."
|
||||
For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#enabling-push-notifications-with-github-mobile)."
|
||||
|
||||
{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %}
|
||||
{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication#verifying-with-github-mobile)." {% endif %}
|
||||
|
||||
## Installing {% data variables.product.prodname_mobile %}
|
||||
|
||||
|
|
@ -49,7 +49,7 @@ You can be simultaneously signed into mobile with one personal account on {% dat
|
|||
|
||||
You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}.
|
||||
|
||||
To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.location.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
|
||||
To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.location.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% ifversion ghes %}"[Release notes](/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
|
||||
|
||||
During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a personal account on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ The following sections list some of the available keyboard shortcuts, organized
|
|||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>S</kbd> or <kbd>/</kbd> | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
|
||||
|<kbd>G</kbd> <kbd>N</kbd> | Go to your notifications. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)."
|
||||
|<kbd>G</kbd> <kbd>N</kbd> | Go to your notifications. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
|
||||
|<kbd>Esc</kbd> | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in
|
||||
{% ifversion command-palette %}|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
|
||||
|
||||
|
|
@ -40,10 +40,10 @@ The following sections list some of the available keyboard shortcuts, organized
|
|||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>G</kbd> <kbd>C</kbd> | Go to the **Code** tab
|
||||
|<kbd>G</kbd> <kbd>I</kbd> | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)."
|
||||
|<kbd>G</kbd> <kbd>I</kbd> | Go to the **Issues** tab. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."
|
||||
|<kbd>G</kbd> <kbd>P</kbd> | Go to the **Pull requests** tab. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
|
||||
|<kbd>G</kbd> <kbd>A</kbd> | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %}
|
||||
|<kbd>G</kbd> <kbd>B</kbd> | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)."
|
||||
|<kbd>G</kbd> <kbd>A</kbd> | Go to the **Actions** tab. For more information, see "[About Actions](/actions/learn-github-actions)."{% endif %}
|
||||
|<kbd>G</kbd> <kbd>B</kbd> | Go to the **Projects** tab. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
|
||||
|<kbd>G</kbd> <kbd>W</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion discussions %}
|
||||
|<kbd>G</kbd> <kbd>G</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
|
||||
|
||||
|
|
@ -80,10 +80,10 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|
|||
|<kbd>T</kbd> | Activates the file finder
|
||||
|<kbd>L</kbd> | Jump to a line in your code
|
||||
|<kbd>W</kbd> | Switch to a new branch or tag
|
||||
|<kbd>Y</kbd> | Expand a URL to its canonical form. For more information, see "[Getting permanent links to files](/articles/getting-permanent-links-to-files)."
|
||||
|<kbd>I</kbd> | Show or hide comments on diffs. For more information, see "[Commenting on the diff of a pull request](/articles/commenting-on-the-diff-of-a-pull-request)."
|
||||
|<kbd>Y</kbd> | Expand a URL to its canonical form. For more information, see "[Getting permanent links to files](/repositories/working-with-files/using-files/getting-permanent-links-to-files)."
|
||||
|<kbd>I</kbd> | Show or hide comments on diffs. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)."
|
||||
|<kbd>A</kbd> | Show or hide annotations on diffs
|
||||
|<kbd>B</kbd> | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)."
|
||||
|<kbd>B</kbd> | Open blame view. For more information, see "[Viewing a file](/repositories/working-with-files/using-files/viewing-a-file)."
|
||||
|
||||
## Comments
|
||||
|
||||
|
|
@ -100,10 +100,10 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|
|||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Inserts Markdown formatting for an ordered list
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list
|
||||
|<kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux) | Submits a comment
|
||||
|<kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd> | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."
|
||||
|<kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd> | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/get-started/writing-on-github/working-with-saved-replies/about-saved-replies)."
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% ifversion fpt or ghec %}
|
||||
|<kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux) | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %}
|
||||
|<kbd>R</kbd> | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." |
|
||||
|<kbd>R</kbd> | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#quoting-text)." |
|
||||
|
||||
## Issue and pull request lists
|
||||
|
||||
|
|
@ -112,24 +112,24 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|
|||
|<kbd>C</kbd> | Create an issue
|
||||
|<kbd>Command</kbd>+<kbd>/</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>/</kbd> (Windows/Linux) | Focus your cursor on the issues or pull requests search bar. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."||
|
||||
|<kbd>U</kbd> | Filter by author
|
||||
|<kbd>L</kbd> | Filter by or edit labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)."
|
||||
|<kbd>Alt</kbd> and click | While filtering by labels, exclude labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)."
|
||||
|<kbd>M</kbd> | Filter by or edit milestones. For more information, see "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)."
|
||||
|<kbd>A</kbd> | Filter by or edit assignee. For more information, see "[Filtering issues and pull requests by assignees](/articles/filtering-issues-and-pull-requests-by-assignees)."
|
||||
|<kbd>L</kbd> | Filter by or edit labels. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."
|
||||
|<kbd>Alt</kbd> and click | While filtering by labels, exclude labels. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."
|
||||
|<kbd>M</kbd> | Filter by or edit milestones. For more information, see "[Filtering issues and pull requests by milestone](/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone)."
|
||||
|<kbd>A</kbd> | Filter by or edit assignee. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."
|
||||
|<kbd>O</kbd> or <kbd>Enter</kbd> | Open issue
|
||||
|
||||
## Issues and pull requests
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------
|
||||
|<kbd>Q</kbd> | Request a reviewer. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review/)."
|
||||
|<kbd>M</kbd> | Set a milestone. For more information, see "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)."
|
||||
|<kbd>L</kbd> | Apply a label. For more information, see "[Applying labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests/)."
|
||||
|<kbd>A</kbd> | Set an assignee. For more information, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/articles/assigning-issues-and-pull-requests-to-other-github-users/)."
|
||||
|<kbd>X</kbd> | Link an issue or pull request from the same repository. For more information, see "[Linking a pull request to an issue](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue/)."
|
||||
|<kbd>Q</kbd> | Request a reviewer. For more information, see "[Requesting a pull request review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)."
|
||||
|<kbd>M</kbd> | Set a milestone. For more information, see "[Associating milestones with issues and pull requests](/issues/using-labels-and-milestones-to-track-work/associating-milestones-with-issues-and-pull-requests)."
|
||||
|<kbd>L</kbd> | Apply a label. For more information, see "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels#applying-a-label)."
|
||||
|<kbd>A</kbd> | Set an assignee. For more information, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)."
|
||||
|<kbd>X</kbd> | Link an issue or pull request from the same repository. For more information, see "[Linking a pull request to an issue](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)."
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %}
|
||||
|<kbd>Alt</kbd> and click | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>Alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
|
||||
|<kbd>Shift</kbd> and click | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
|
||||
|<kbd>Command</kbd> and click (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and click (Windows/Linux) | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>Command</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
|
||||
|<kbd>Alt</kbd> and click | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>Alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists)."
|
||||
|<kbd>Shift</kbd> and click | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists)."
|
||||
|<kbd>Command</kbd> and click (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and click (Windows/Linux) | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>Command</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists)."{% endif %}
|
||||
|
||||
## "Files changed" tab in pull requests
|
||||
|
||||
|
|
@ -139,7 +139,7 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
|
|||
|<kbd>T</kbd> | Move your cursor to the "Filter changed files" field
|
||||
|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Enter</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Enter</kbd> (Windows/Linux) | Submit a review comment |
|
||||
|<kbd>Option</kbd> and click (Mac) or <kbd>Alt</kbd> and click (Windows/Linux) | Toggle between collapsing and expanding all outdated or resolved review comments in a pull request (for example, by holding down <kbd>Alt</kbd> and clicking **Show outdated** or **Hide outdated**) |
|
||||
|Click, then <kbd>Shift</kbd> and click | Comment on multiple lines of a pull request by clicking a line number, holding <kbd>Shift</kbd>, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|
|
||||
|Click, then <kbd>Shift</kbd> and click | Comment on multiple lines of a pull request by clicking a line number, holding <kbd>Shift</kbd>, then clicking another line number. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Most often, connection problems occur because a firewall, proxy server, corporat
|
|||
|
||||
## Allowing {% data variables.product.prodname_dotcom %}'s IP addresses
|
||||
|
||||
Make sure your network is configured to allow {% data variables.product.prodname_dotcom %}'s IP addresses. For more information, see "[About {% data variables.product.prodname_dotcom %}'s IP addresses](/articles/about-github-s-ip-addresses)."
|
||||
Make sure your network is configured to allow {% data variables.product.prodname_dotcom %}'s IP addresses. For more information, see "[About {% data variables.product.prodname_dotcom %}'s IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)."
|
||||
|
||||
## Using a company or organization's network
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ If you're having connectivity problems on your company or organization's network
|
|||
|
||||
If you're unable to verify with the captcha:
|
||||
- Ensure JavaScript is enabled on your browser.
|
||||
- Ensure your browser is supported. If your browser isn't supported, upgrade your browser or install a supported browser. For a list of supported browsers, see "[Supported browsers](/articles/supported-browsers)."
|
||||
- Ensure your browser is supported. If your browser isn't supported, upgrade your browser or install a supported browser. For a list of supported browsers, see "[Supported browsers](/get-started/using-github/supported-browsers)."
|
||||
- Ensure your network configuration is not blocking https://octocaptcha.com/ or https://arkoselabs.com/. If you're behind a corporate firewall, contact your IT administrator to allow those domains. To verify access to these domains, visit https://octocaptcha.com/test and ensure the text "Connection successfully made!" is displayed, then visit https://client-demo.arkoselabs.com/github and ensure you are able to load the captcha.
|
||||
- Ensure your browser does not have plug-ins or extensions that may be interfering with GitHub. If so, temporarily disable the plug-ins or extensions during captcha verification.
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ Switching from cloning via SSH to cloning via HTTPS, or vice versa may improve c
|
|||
|
||||
If you prefer to use SSH but the port is blocked, you can use an alternative port. For more information, see "[Using SSH over the HTTPS port](/authentication/troubleshooting-ssh/using-ssh-over-the-https-port)".
|
||||
|
||||
If you're encountering timeouts with SSH, see "[Error: Bad file number](/articles/error-bad-file-number)."
|
||||
If you're encountering timeouts with SSH, see "[Error: Bad file number](/authentication/troubleshooting-ssh/error-bad-file-number)."
|
||||
|
||||
## Troubleshooting slow downloads and intermittent slow connections
|
||||
|
||||
|
|
|
|||
|
|
@ -6040,6 +6040,51 @@ type ConvertedToDiscussionEvent implements Node {
|
|||
id: ID!
|
||||
}
|
||||
|
||||
"""
|
||||
Autogenerated input type of CopyProjectV2
|
||||
"""
|
||||
input CopyProjectV2Input {
|
||||
"""
|
||||
A unique identifier for the client performing the mutation.
|
||||
"""
|
||||
clientMutationId: String
|
||||
|
||||
"""
|
||||
Include draft issues in the new project
|
||||
"""
|
||||
includeDraftIssues: Boolean = false
|
||||
|
||||
"""
|
||||
The owner ID of the new project.
|
||||
"""
|
||||
ownerId: ID! @possibleTypes(concreteTypes: ["Organization", "User"], abstractType: "OrganizationOrUser")
|
||||
|
||||
"""
|
||||
The ID of the source Project to copy.
|
||||
"""
|
||||
projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"])
|
||||
|
||||
"""
|
||||
The title of the project.
|
||||
"""
|
||||
title: String!
|
||||
}
|
||||
|
||||
"""
|
||||
Autogenerated return type of CopyProjectV2
|
||||
"""
|
||||
type CopyProjectV2Payload {
|
||||
"""
|
||||
A unique identifier for the client performing the mutation.
|
||||
"""
|
||||
clientMutationId: String
|
||||
|
||||
"""
|
||||
The copied project.
|
||||
"""
|
||||
projectV2: ProjectV2
|
||||
}
|
||||
|
||||
"""
|
||||
Autogenerated input type of CreateAttributionInvitation
|
||||
"""
|
||||
|
|
@ -20240,6 +20285,16 @@ type Mutation {
|
|||
input: ConvertPullRequestToDraftInput!
|
||||
): ConvertPullRequestToDraftPayload
|
||||
|
||||
"""
|
||||
Copy a project.
|
||||
"""
|
||||
copyProjectV2(
|
||||
"""
|
||||
Parameters for CopyProjectV2
|
||||
"""
|
||||
input: CopyProjectV2Input!
|
||||
): CopyProjectV2Payload
|
||||
|
||||
"""
|
||||
Invites a user to claim reattributable data
|
||||
"""
|
||||
|
|
|
|||
|
|
@ -6040,6 +6040,51 @@ type ConvertedToDiscussionEvent implements Node {
|
|||
id: ID!
|
||||
}
|
||||
|
||||
"""
|
||||
Autogenerated input type of CopyProjectV2
|
||||
"""
|
||||
input CopyProjectV2Input {
|
||||
"""
|
||||
A unique identifier for the client performing the mutation.
|
||||
"""
|
||||
clientMutationId: String
|
||||
|
||||
"""
|
||||
Include draft issues in the new project
|
||||
"""
|
||||
includeDraftIssues: Boolean = false
|
||||
|
||||
"""
|
||||
The owner ID of the new project.
|
||||
"""
|
||||
ownerId: ID! @possibleTypes(concreteTypes: ["Organization", "User"], abstractType: "OrganizationOrUser")
|
||||
|
||||
"""
|
||||
The ID of the source Project to copy.
|
||||
"""
|
||||
projectId: ID! @possibleTypes(concreteTypes: ["ProjectV2"])
|
||||
|
||||
"""
|
||||
The title of the project.
|
||||
"""
|
||||
title: String!
|
||||
}
|
||||
|
||||
"""
|
||||
Autogenerated return type of CopyProjectV2
|
||||
"""
|
||||
type CopyProjectV2Payload {
|
||||
"""
|
||||
A unique identifier for the client performing the mutation.
|
||||
"""
|
||||
clientMutationId: String
|
||||
|
||||
"""
|
||||
The copied project.
|
||||
"""
|
||||
projectV2: ProjectV2
|
||||
}
|
||||
|
||||
"""
|
||||
Autogenerated input type of CreateAttributionInvitation
|
||||
"""
|
||||
|
|
@ -20240,6 +20285,16 @@ type Mutation {
|
|||
input: ConvertPullRequestToDraftInput!
|
||||
): ConvertPullRequestToDraftPayload
|
||||
|
||||
"""
|
||||
Copy a project.
|
||||
"""
|
||||
copyProjectV2(
|
||||
"""
|
||||
Parameters for CopyProjectV2
|
||||
"""
|
||||
input: CopyProjectV2Input!
|
||||
): CopyProjectV2Payload
|
||||
|
||||
"""
|
||||
Invites a user to claim reattributable data
|
||||
"""
|
||||
|
|
|
|||
|
|
@ -73,6 +73,7 @@ secret_scanning:
|
|||
- '/code-security/secret-scanning/secret-scanning-patterns'
|
||||
- '{% ifversion secret-scanning-push-protection %}/code-security/secret-scanning/protecting-pushes-with-secret-scanning{% endif %}'
|
||||
- '{% ifversion secret-scanning-push-protection %}/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection{% endif %}'
|
||||
- '/code-security/secret-scanning/troubleshooting-secret-scanning'
|
||||
|
||||
# Security overview feature available in GHEC and GHES 3.2+, so other articles hidden to hide the learning path in other versions
|
||||
security_alerts:
|
||||
|
|
|
|||
|
|
@ -3,21 +3,4 @@ For a specific job, you can use `jobs.<job_id>.permissions` to modify the defaul
|
|||
By specifying the permission within a job definition, you can configure a different set of permissions for the `GITHUB_TOKEN` for each job, if required. Alternatively, you can specify the permissions for all jobs in the workflow. For information on defining permissions at the workflow level, see [`permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions).
|
||||
|
||||
{% data reusables.actions.github-token-available-permissions %}
|
||||
{% data reusables.actions.forked-write-permission %}
|
||||
|
||||
#### Example: Setting permissions for a specific job
|
||||
|
||||
This example shows permissions being set for the `GITHUB_TOKEN` that will only apply to the job named `stale`. Write access is granted for the `issues` and `pull-requests` scopes. All other scopes will have no access.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
stale:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
permissions:
|
||||
issues: write
|
||||
pull-requests: write
|
||||
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-stale %}
|
||||
```
|
||||
{% data reusables.actions.forked-write-permission %}
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
Use `jobs.<job_id>.needs` to identify any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to continue. If a run contains a series of jobs that need each other, a failure applies to all jobs in the dependency chain from the point of failure onwards.
|
||||
|
||||
#### Example: Requiring successful dependent jobs
|
||||
### Example: Requiring successful dependent jobs
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
|
|
@ -19,7 +19,7 @@ The jobs in this example run sequentially:
|
|||
2. `job2`
|
||||
3. `job3`
|
||||
|
||||
#### Example: Not requiring successful dependent jobs
|
||||
### Example: Not requiring successful dependent jobs
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
|
|
|
|||
|
|
@ -0,0 +1,9 @@
|
|||
```yaml
|
||||
jobs:
|
||||
job1:
|
||||
runs-on: ubuntu-latest
|
||||
defaults:
|
||||
run:
|
||||
shell: bash
|
||||
working-directory: scripts
|
||||
```
|
||||
|
|
@ -2,16 +2,4 @@ Use `jobs.<job_id>.defaults.run` to provide default `shell` and `working-directo
|
|||
|
||||
You can provide default `shell` and `working-directory` options for all [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) steps in a job. You can also set default settings for `run` for the entire workflow. For more information, see [`jobs.defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#defaultsrun). You cannot use contexts or expressions in this keyword.
|
||||
|
||||
{% data reusables.actions.defaults-override %}
|
||||
|
||||
#### Example: Setting default `run` step options for a job
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
job1:
|
||||
runs-on: ubuntu-latest
|
||||
defaults:
|
||||
run:
|
||||
shell: bash
|
||||
working-directory: scripts
|
||||
```
|
||||
{% data reusables.actions.defaults-override %}
|
||||
|
|
@ -0,0 +1,14 @@
|
|||
This example shows permissions being set for the `GITHUB_TOKEN` that will only apply to the job named `stale`. Write access is granted for the `issues` and `pull-requests` scopes. All other scopes will have no access.
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
stale:
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
permissions:
|
||||
issues: write
|
||||
pull-requests: write
|
||||
|
||||
steps:
|
||||
- uses: {% data reusables.actions.action-stale %}
|
||||
```
|
||||
|
|
@ -6,4 +6,8 @@ Any navigation to resources protected by an IP allow list will be filtered by th
|
|||
* {% data variables.product.pat_generic_caps %}
|
||||
* SSH keys
|
||||
|
||||
All user credentials, including those belonging to administrators, are subject to IP allow list checks. IP allow lists are not enforced on traffic directed to public repositories.
|
||||
All user credentials, including those belonging to administrators, are subject to IP allow list checks.
|
||||
|
||||
Only organization-owned repositories are subject to IP allow list checks. IP allow list restrictions are not enforced for repositories owned by a {% data variables.enterprise.prodname_managed_user %}.
|
||||
|
||||
IP allow lists are not enforced on traffic directed to public repositories.
|
||||
|
|
|
|||
|
|
@ -0,0 +1 @@
|
|||
Older versions of certain tokens may not be supported by push protection as these tokens may generate a higher number of false positives than their most recent version. Push protection may also not apply to legacy tokens. For tokens such as Azure Storage Keys, {% data variables.product.prodname_dotcom %} only supports _recently created_ tokens, not tokens that match the legacy patterns.
|
||||
|
|
@ -1 +1 @@
|
|||
If access to a resource requires paired credentials, then secret scanning will create an alert only when both parts of the pair are detected in the same file. This ensures that the most critical leaks are not hidden behind information about partial leaks.
|
||||
If access to a resource requires paired credentials, then secret scanning will create an alert only when both parts of the pair are detected in the same file. This ensures that the most critical leaks are not hidden behind information about partial leaks. Pair matching also helps reduce false positives since both elements of a pair must be used together to access the provider's resource.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,19 @@
|
|||
[
|
||||
{
|
||||
"schemaChanges": [
|
||||
{
|
||||
"title": "The GraphQL schema includes these changes:",
|
||||
"changes": [
|
||||
"<p>Type 'CopyProjectV2Input' was added</p>",
|
||||
"<p>Type 'CopyProjectV2Payload' was added</p>",
|
||||
"<p>Field 'copyProjectV2<code>was added to object type</code>Mutation'</p>"
|
||||
]
|
||||
}
|
||||
],
|
||||
"previewChanges": [],
|
||||
"upcomingChanges": [],
|
||||
"date": "2023-02-05"
|
||||
},
|
||||
{
|
||||
"schemaChanges": [
|
||||
{
|
||||
|
|
|
|||
|
|
@ -813,148 +813,6 @@
|
|||
"href": "/graphql/overview/schema-previews#team-review-assignments-preview"
|
||||
}
|
||||
],
|
||||
"ghes-3.3": [
|
||||
{
|
||||
"title": "Access to package version deletion preview",
|
||||
"description": "This preview adds support for the DeletePackageVersion mutation which enables deletion of private package versions.",
|
||||
"toggled_by": "package-deletes-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.deletePackageVersion"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/pe-package-registry"
|
||||
],
|
||||
"accept_header": "application/vnd.github.package-deletes-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#access-to-package-version-deletion-preview"
|
||||
},
|
||||
{
|
||||
"title": "Deployments preview",
|
||||
"description": "This preview adds support for deployments mutations and new deployments features.",
|
||||
"toggled_by": "flash-preview",
|
||||
"toggled_on": [
|
||||
"DeploymentStatus.environment",
|
||||
"Mutation.createDeploymentStatus",
|
||||
"Mutation.createDeployment"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/c2c-actions-service"
|
||||
],
|
||||
"accept_header": "application/vnd.github.flash-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#deployments-preview"
|
||||
},
|
||||
{
|
||||
"title": "Merge info preview",
|
||||
"description": "This preview adds support for accessing fields that provide more detailed information about a pull request's merge state.",
|
||||
"toggled_by": "merge-info-preview",
|
||||
"toggled_on": [
|
||||
"PullRequest.canBeRebased",
|
||||
"PullRequest.mergeStateStatus"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/pe-pull-requests"
|
||||
],
|
||||
"accept_header": "application/vnd.github.merge-info-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#merge-info-preview"
|
||||
},
|
||||
{
|
||||
"title": "Update refs preview",
|
||||
"description": "This preview adds support for updating multiple refs in a single operation.",
|
||||
"toggled_by": "update-refs-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.updateRefs",
|
||||
"GitRefname",
|
||||
"RefUpdate"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/reponauts"
|
||||
],
|
||||
"accept_header": "application/vnd.github.update-refs-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#update-refs-preview"
|
||||
},
|
||||
{
|
||||
"title": "Project event details preview",
|
||||
"description": "This preview adds project, project card, and project column details to project-related issue events.",
|
||||
"toggled_by": "starfox-preview",
|
||||
"toggled_on": [
|
||||
"AddedToProjectEvent.project",
|
||||
"AddedToProjectEvent.projectCard",
|
||||
"AddedToProjectEvent.projectColumnName",
|
||||
"ConvertedNoteToIssueEvent.project",
|
||||
"ConvertedNoteToIssueEvent.projectCard",
|
||||
"ConvertedNoteToIssueEvent.projectColumnName",
|
||||
"MovedColumnsInProjectEvent.project",
|
||||
"MovedColumnsInProjectEvent.projectCard",
|
||||
"MovedColumnsInProjectEvent.projectColumnName",
|
||||
"MovedColumnsInProjectEvent.previousProjectColumnName",
|
||||
"RemovedFromProjectEvent.project",
|
||||
"RemovedFromProjectEvent.projectColumnName"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/github-projects"
|
||||
],
|
||||
"accept_header": "application/vnd.github.starfox-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#project-event-details-preview"
|
||||
},
|
||||
{
|
||||
"title": "Create content attachments preview",
|
||||
"description": "This preview adds support for creating content attachments.",
|
||||
"toggled_by": "corsair-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.createContentAttachment"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/feature-lifecycle"
|
||||
],
|
||||
"accept_header": "application/vnd.github.corsair-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#create-content-attachments-preview"
|
||||
},
|
||||
{
|
||||
"title": "Labels preview",
|
||||
"description": "This preview adds support for adding, updating, creating and deleting labels.",
|
||||
"toggled_by": "bane-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.createLabel",
|
||||
"Mutation.deleteLabel",
|
||||
"Mutation.updateLabel"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/pe-pull-requests"
|
||||
],
|
||||
"accept_header": "application/vnd.github.bane-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#labels-preview"
|
||||
},
|
||||
{
|
||||
"title": "Import project preview",
|
||||
"description": "This preview adds support for importing projects.",
|
||||
"toggled_by": "slothette-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.importProject"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/pe-issues-projects"
|
||||
],
|
||||
"accept_header": "application/vnd.github.slothette-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#import-project-preview"
|
||||
},
|
||||
{
|
||||
"title": "Team review assignments preview",
|
||||
"description": "This preview adds support for updating the settings for team review assignment.",
|
||||
"toggled_by": "stone-crop-preview",
|
||||
"toggled_on": [
|
||||
"Mutation.updateTeamReviewAssignment",
|
||||
"TeamReviewAssignmentAlgorithm",
|
||||
"Team.reviewRequestDelegationEnabled",
|
||||
"Team.reviewRequestDelegationAlgorithm",
|
||||
"Team.reviewRequestDelegationMemberCount",
|
||||
"Team.reviewRequestDelegationNotifyTeam"
|
||||
],
|
||||
"owning_teams": [
|
||||
"@github/pe-pull-requests"
|
||||
],
|
||||
"accept_header": "application/vnd.github.stone-crop-preview+json",
|
||||
"href": "/graphql/overview/schema-previews#team-review-assignments-preview"
|
||||
}
|
||||
],
|
||||
"ghae": [
|
||||
{
|
||||
"title": "Access to package version deletion preview",
|
||||
|
|
|
|||
|
|
@ -2170,6 +2170,40 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"name": "copyProjectV2",
|
||||
"kind": "mutations",
|
||||
"id": "copyprojectv2",
|
||||
"href": "/graphql/reference/mutations#copyprojectv2",
|
||||
"description": "<p>Copy a project.</p>",
|
||||
"inputFields": [
|
||||
{
|
||||
"name": "input",
|
||||
"type": "CopyProjectV2Input!",
|
||||
"id": "copyprojectv2input",
|
||||
"kind": "input-objects",
|
||||
"href": "/graphql/reference/input-objects#copyprojectv2input"
|
||||
}
|
||||
],
|
||||
"returnFields": [
|
||||
{
|
||||
"name": "clientMutationId",
|
||||
"type": "String",
|
||||
"id": "string",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#string",
|
||||
"description": "<p>A unique identifier for the client performing the mutation.</p>"
|
||||
},
|
||||
{
|
||||
"name": "projectV2",
|
||||
"type": "ProjectV2",
|
||||
"id": "projectv2",
|
||||
"kind": "objects",
|
||||
"href": "/graphql/reference/objects#projectv2",
|
||||
"description": "<p>The copied project.</p>"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"name": "createAttributionInvitation",
|
||||
"kind": "mutations",
|
||||
|
|
@ -83751,6 +83785,57 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"name": "CopyProjectV2Input",
|
||||
"kind": "inputObjects",
|
||||
"id": "copyprojectv2input",
|
||||
"href": "/graphql/reference/input-objects#copyprojectv2input",
|
||||
"description": "<p>Autogenerated input type of CopyProjectV2.</p>",
|
||||
"inputFields": [
|
||||
{
|
||||
"name": "clientMutationId",
|
||||
"description": "<p>A unique identifier for the client performing the mutation.</p>",
|
||||
"type": "String",
|
||||
"id": "string",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#string"
|
||||
},
|
||||
{
|
||||
"name": "includeDraftIssues",
|
||||
"description": "<p>Include draft issues in the new project.</p>",
|
||||
"type": "Boolean",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "ownerId",
|
||||
"description": "<p>The owner ID of the new project.</p>",
|
||||
"type": "ID!",
|
||||
"id": "id",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#id",
|
||||
"isDeprecated": false
|
||||
},
|
||||
{
|
||||
"name": "projectId",
|
||||
"description": "<p>The ID of the source Project to copy.</p>",
|
||||
"type": "ID!",
|
||||
"id": "id",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#id",
|
||||
"isDeprecated": false
|
||||
},
|
||||
{
|
||||
"name": "title",
|
||||
"description": "<p>The title of the project.</p>",
|
||||
"type": "String!",
|
||||
"id": "string",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#string"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"name": "CreateAttributionInvitationInput",
|
||||
"kind": "inputObjects",
|
||||
|
|
|
|||
|
|
@ -2170,6 +2170,40 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"name": "copyProjectV2",
|
||||
"kind": "mutations",
|
||||
"id": "copyprojectv2",
|
||||
"href": "/graphql/reference/mutations#copyprojectv2",
|
||||
"description": "<p>Copy a project.</p>",
|
||||
"inputFields": [
|
||||
{
|
||||
"name": "input",
|
||||
"type": "CopyProjectV2Input!",
|
||||
"id": "copyprojectv2input",
|
||||
"kind": "input-objects",
|
||||
"href": "/graphql/reference/input-objects#copyprojectv2input"
|
||||
}
|
||||
],
|
||||
"returnFields": [
|
||||
{
|
||||
"name": "clientMutationId",
|
||||
"type": "String",
|
||||
"id": "string",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#string",
|
||||
"description": "<p>A unique identifier for the client performing the mutation.</p>"
|
||||
},
|
||||
{
|
||||
"name": "projectV2",
|
||||
"type": "ProjectV2",
|
||||
"id": "projectv2",
|
||||
"kind": "objects",
|
||||
"href": "/graphql/reference/objects#projectv2",
|
||||
"description": "<p>The copied project.</p>"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"name": "createAttributionInvitation",
|
||||
"kind": "mutations",
|
||||
|
|
@ -83751,6 +83785,57 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"name": "CopyProjectV2Input",
|
||||
"kind": "inputObjects",
|
||||
"id": "copyprojectv2input",
|
||||
"href": "/graphql/reference/input-objects#copyprojectv2input",
|
||||
"description": "<p>Autogenerated input type of CopyProjectV2.</p>",
|
||||
"inputFields": [
|
||||
{
|
||||
"name": "clientMutationId",
|
||||
"description": "<p>A unique identifier for the client performing the mutation.</p>",
|
||||
"type": "String",
|
||||
"id": "string",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#string"
|
||||
},
|
||||
{
|
||||
"name": "includeDraftIssues",
|
||||
"description": "<p>Include draft issues in the new project.</p>",
|
||||
"type": "Boolean",
|
||||
"id": "boolean",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#boolean"
|
||||
},
|
||||
{
|
||||
"name": "ownerId",
|
||||
"description": "<p>The owner ID of the new project.</p>",
|
||||
"type": "ID!",
|
||||
"id": "id",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#id",
|
||||
"isDeprecated": false
|
||||
},
|
||||
{
|
||||
"name": "projectId",
|
||||
"description": "<p>The ID of the source Project to copy.</p>",
|
||||
"type": "ID!",
|
||||
"id": "id",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#id",
|
||||
"isDeprecated": false
|
||||
},
|
||||
{
|
||||
"name": "title",
|
||||
"description": "<p>The title of the project.</p>",
|
||||
"type": "String!",
|
||||
"id": "string",
|
||||
"kind": "scalars",
|
||||
"href": "/graphql/reference/scalars#string"
|
||||
}
|
||||
]
|
||||
},
|
||||
{
|
||||
"name": "CreateAttributionInvitationInput",
|
||||
"kind": "inputObjects",
|
||||
|
|
|
|||
|
|
@ -1131,150 +1131,6 @@
|
|||
}
|
||||
]
|
||||
},
|
||||
"ghes-3.3": {
|
||||
"2021-10-01": [
|
||||
{
|
||||
"location": "ReactionGroup.users",
|
||||
"description": "<p><code>users</code> will be removed. Use the <code>reactors</code> field instead.</p>",
|
||||
"reason": "<p>Reactors can now be mannequins, bots, and organizations.</p>",
|
||||
"date": "2021-10-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "synthead"
|
||||
}
|
||||
],
|
||||
"2021-06-21": [
|
||||
{
|
||||
"location": "PackageType.DOCKER",
|
||||
"description": "<p><code>DOCKER</code> will be removed.</p>",
|
||||
"reason": "<p>DOCKER will be removed from this enum as this type will be migrated to only be used by the Packages REST API.</p>",
|
||||
"date": "2021-06-21",
|
||||
"criticality": "breaking",
|
||||
"owner": "reybard"
|
||||
}
|
||||
],
|
||||
"2021-01-01": [
|
||||
{
|
||||
"location": "MergeStateStatus.DRAFT",
|
||||
"description": "<p><code>DRAFT</code> will be removed. Use PullRequest.isDraft instead.</p>",
|
||||
"reason": "<p>DRAFT state will be removed from this enum and <code>isDraft</code> should be used instead</p>",
|
||||
"date": "2021-01-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "nplasterer"
|
||||
},
|
||||
{
|
||||
"location": "EnterprisePendingCollaboratorEdge.isUnlicensed",
|
||||
"description": "<p><code>isUnlicensed</code> will be removed.</p>",
|
||||
"reason": "<p>All pending collaborators consume a license</p>",
|
||||
"date": "2021-01-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "BrentWheeldon"
|
||||
},
|
||||
{
|
||||
"location": "EnterpriseOutsideCollaboratorEdge.isUnlicensed",
|
||||
"description": "<p><code>isUnlicensed</code> will be removed.</p>",
|
||||
"reason": "<p>All outside collaborators consume a license</p>",
|
||||
"date": "2021-01-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "BrentWheeldon"
|
||||
},
|
||||
{
|
||||
"location": "EnterpriseMemberEdge.isUnlicensed",
|
||||
"description": "<p><code>isUnlicensed</code> will be removed.</p>",
|
||||
"reason": "<p>All members consume a license</p>",
|
||||
"date": "2021-01-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "BrentWheeldon"
|
||||
}
|
||||
],
|
||||
"2020-10-01": [
|
||||
{
|
||||
"location": "RepositoryInvitationOrderField.INVITEE_LOGIN",
|
||||
"description": "<p><code>INVITEE_LOGIN</code> will be removed.</p>",
|
||||
"reason": "<p><code>INVITEE_LOGIN</code> is no longer a valid field value. Repository invitations can now be associated with an email, not only an invitee.</p>",
|
||||
"date": "2020-10-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "jdennes"
|
||||
},
|
||||
{
|
||||
"location": "PullRequest.timeline",
|
||||
"description": "<p><code>timeline</code> will be removed. Use PullRequest.timelineItems instead.</p>",
|
||||
"reason": "<p><code>timeline</code> will be removed</p>",
|
||||
"date": "2020-10-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "mikesea"
|
||||
},
|
||||
{
|
||||
"location": "Issue.timeline",
|
||||
"description": "<p><code>timeline</code> will be removed. Use Issue.timelineItems instead.</p>",
|
||||
"reason": "<p><code>timeline</code> will be removed</p>",
|
||||
"date": "2020-10-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "mikesea"
|
||||
},
|
||||
{
|
||||
"location": "EnterpriseOwnerInfo.pendingCollaborators",
|
||||
"description": "<p><code>pendingCollaborators</code> will be removed. Use the <code>pendingCollaboratorInvitations</code> field instead.</p>",
|
||||
"reason": "<p>Repository invitations can now be associated with an email, not only an invitee.</p>",
|
||||
"date": "2020-10-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "jdennes"
|
||||
}
|
||||
],
|
||||
"2020-07-01": [
|
||||
{
|
||||
"location": "EnterprisePendingMemberInvitationEdge.isUnlicensed",
|
||||
"description": "<p><code>isUnlicensed</code> will be removed.</p>",
|
||||
"reason": "<p>All pending members consume a license</p>",
|
||||
"date": "2020-07-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "BrentWheeldon"
|
||||
}
|
||||
],
|
||||
"2020-01-01": [
|
||||
{
|
||||
"location": "UnassignedEvent.user",
|
||||
"description": "<p><code>user</code> will be removed. Use the <code>assignee</code> field instead.</p>",
|
||||
"reason": "<p>Assignees can now be mannequins.</p>",
|
||||
"date": "2020-01-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "tambling"
|
||||
},
|
||||
{
|
||||
"location": "EnterpriseBillingInfo.seats",
|
||||
"description": "<p><code>seats</code> will be removed. Use EnterpriseBillingInfo.totalLicenses instead.</p>",
|
||||
"reason": "<p><code>seats</code> will be replaced with <code>totalLicenses</code> to provide more clarity on the value being returned</p>",
|
||||
"date": "2020-01-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "BlakeWilliams"
|
||||
},
|
||||
{
|
||||
"location": "EnterpriseBillingInfo.availableSeats",
|
||||
"description": "<p><code>availableSeats</code> will be removed. Use EnterpriseBillingInfo.totalAvailableLicenses instead.</p>",
|
||||
"reason": "<p><code>availableSeats</code> will be replaced with <code>totalAvailableLicenses</code> to provide more clarity on the value being returned</p>",
|
||||
"date": "2020-01-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "BlakeWilliams"
|
||||
},
|
||||
{
|
||||
"location": "AssignedEvent.user",
|
||||
"description": "<p><code>user</code> will be removed. Use the <code>assignee</code> field instead.</p>",
|
||||
"reason": "<p>Assignees can now be mannequins.</p>",
|
||||
"date": "2020-01-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "tambling"
|
||||
}
|
||||
],
|
||||
"2019-04-01": [
|
||||
{
|
||||
"location": "LegacyMigration.uploadUrlTemplate",
|
||||
"description": "<p><code>uploadUrlTemplate</code> will be removed. Use <code>uploadUrl</code> instead.</p>",
|
||||
"reason": "<p><code>uploadUrlTemplate</code> is being removed because it is not a standard URL and adds an extra user step.</p>",
|
||||
"date": "2019-04-01",
|
||||
"criticality": "breaking",
|
||||
"owner": "tambling"
|
||||
}
|
||||
]
|
||||
},
|
||||
"ghae": {
|
||||
"2023-07-01": [
|
||||
{
|
||||
|
|
|
|||
|
|
@ -1108,10 +1108,6 @@
|
|||
"/rest/enterprise-admin#delete-a-user": "/rest/enterprise-admin/users#delete-a-user",
|
||||
"/rest/enterprise-admin#create-an-impersonation-oauth-token": "/rest/enterprise-admin/users#create-an-impersonation-oauth-token",
|
||||
"/rest/enterprise-admin#delete-an-impersonation-oauth-token": "/rest/enterprise-admin/users#delete-an-impersonation-oauth-token",
|
||||
"/rest/apps#revoke-a-grant-for-an-application": "/rest/apps/oauth-applications#revoke-a-grant-for-an-application",
|
||||
"/rest/apps#check-an-authorization": "/rest/apps/oauth-applications#check-an-authorization",
|
||||
"/rest/apps#reset-an-authorization": "/rest/apps/oauth-applications#reset-an-authorization",
|
||||
"/rest/apps#revoke-an-authorization-for-an-application": "/rest/apps/oauth-applications#revoke-an-authorization-for-an-application",
|
||||
"/rest/enterprise-admin/announcement#get-the-global-announcement-banner": "/rest/enterprise-admin/announcement#get-the-global-announcement-banner",
|
||||
"/rest/enterprise-admin#announcement": "/rest/enterprise-admin/announcement",
|
||||
"/rest/enterprise-admin/announcement#set-the-global-announcement-banner": "/rest/enterprise-admin/announcement#set-the-global-announcement-banner",
|
||||
|
|
@ -1133,12 +1129,12 @@
|
|||
"/rest/enterprise-admin#get-a-pre-receive-hook-for-an-organization": "/rest/enterprise-admin/org-pre-receive-hooks#get-a-pre-receive-hook-for-an-organization",
|
||||
"/rest/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization": "/rest/enterprise-admin/org-pre-receive-hooks#update-pre-receive-hook-enforcement-for-an-organization",
|
||||
"/rest/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization": "/rest/enterprise-admin/org-pre-receive-hooks#remove-pre-receive-hook-enforcement-for-an-organization",
|
||||
"/rest/apps#create-a-content-attachment": "/rest/apps/installations#create-a-content-attachment",
|
||||
"/rest/enterprise-admin#list-pre-receive-hooks-for-a-repository": "/rest/enterprise-admin/repo-pre-receive-hooks#list-pre-receive-hooks-for-a-repository",
|
||||
"/rest/enterprise-admin#repo-pre-receive-hooks": "/rest/enterprise-admin/repo-pre-receive-hooks",
|
||||
"/rest/enterprise-admin#get-a-pre-receive-hook-for-a-repository": "/rest/enterprise-admin/repo-pre-receive-hooks#get-a-pre-receive-hook-for-a-repository",
|
||||
"/rest/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository": "/rest/enterprise-admin/repo-pre-receive-hooks#update-pre-receive-hook-enforcement-for-a-repository",
|
||||
"/rest/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository": "/rest/enterprise-admin/repo-pre-receive-hooks#remove-pre-receive-hook-enforcement-for-a-repository",
|
||||
"/rest/repos#list-repository-cache-replication-status": "/rest/repos/repos#list-repository-cache-replication-status",
|
||||
"/rest/enterprise-admin#get-the-configuration-status": "/rest/enterprise-admin/management-console#get-the-configuration-status",
|
||||
"/rest/enterprise-admin#management-console": "/rest/enterprise-admin/management-console",
|
||||
"/rest/enterprise-admin#start-a-configuration-process": "/rest/enterprise-admin/management-console#start-a-configuration-process",
|
||||
|
|
@ -1155,7 +1151,6 @@
|
|||
"/rest/enterprise-admin#demote-a-site-administrator": "/rest/enterprise-admin/users#demote-a-site-administrator",
|
||||
"/rest/enterprise-admin#suspend-a-user": "/rest/enterprise-admin/users#suspend-a-user",
|
||||
"/rest/enterprise-admin#unsuspend-a-user": "/rest/enterprise-admin/users#unsuspend-a-user",
|
||||
"/rest/repos#list-repository-cache-replication-status": "/rest/repos/repos#list-repository-cache-replication-status",
|
||||
"/rest/actions#get-github-actions-cache-usage-policy-for-an-enterprise": "/rest/actions/cache#get-github-actions-cache-usage-policy-for-an-enterprise",
|
||||
"/rest/actions#set-github-actions-cache-usage-policy-for-an-enterprise": "/rest/actions/cache#set-github-actions-cache-usage-policy-for-an-enterprise",
|
||||
"/rest/actions#get-github-actions-cache-usage-policy-for-a-repository": "/rest/actions/cache#get-github-actions-cache-usage-policy-for-a-repository",
|
||||
|
|
@ -1172,5 +1167,6 @@
|
|||
"/rest/enterprise-admin#get-scim-provisioning-information-for-an-enterprise-user": "/rest/enterprise-admin/scim#get-scim-provisioning-information-for-an-enterprise-user",
|
||||
"/rest/enterprise-admin#set-scim-information-for-a-provisioned-enterprise-user": "/rest/enterprise-admin/scim#set-scim-information-for-a-provisioned-enterprise-user",
|
||||
"/rest/enterprise-admin#update-an-attribute-for-a-scim-enterprise-user": "/rest/enterprise-admin/scim#update-an-attribute-for-a-scim-enterprise-user",
|
||||
"/rest/enterprise-admin#delete-a-scim-user-from-an-enterprise": "/rest/enterprise-admin/scim#delete-a-scim-user-from-an-enterprise"
|
||||
"/rest/enterprise-admin#delete-a-scim-user-from-an-enterprise": "/rest/enterprise-admin/scim#delete-a-scim-user-from-an-enterprise",
|
||||
"/rest/apps#reset-an-authorization": "/rest/apps/oauth-applications#reset-an-authorization"
|
||||
}
|
||||
Разница между файлами не показана из-за своего большого размера
Загрузить разницу
Загрузка…
Ссылка в новой задаче