Merge branch 'main' into copilot

Author: ashis-baral

content/actions/reference/workflows-and-actions/metadata-syntax.md

@@ -399,7 +399,7 @@ runs:
 
 ### `runs.pre-entrypoint`
 
-**Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
+**Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if-for-docker-container-actions).
 
 The runtime specified with the [`using`](#runsusing-for-docker-container-actions) syntax will execute this file.
 
@@ -415,6 +415,21 @@ runs:
   entrypoint: 'main.sh'
 ```
 
+### `runs.pre-if` for Docker container actions
+
+**Optional** Allows you to define conditions for the `pre-entrypoint:` action execution. The `pre-entrypoint:` action will only run if the conditions in `pre-if` are met. If not set, then `pre-if` defaults to `always()`.
+
+In this example, the `pre-entrypoint:` action runs only on Linux-based runners:
+
+```yaml
+runs:
+  using: 'docker'
+  image: 'Dockerfile'
+  pre-entrypoint: 'setup.sh'
+  pre-if: runner.os == 'linux'
+  entrypoint: 'main.sh'
+```
+
 ### `runs.image`
 
 **Required** The Docker image to use as the container to run the action. The value can be the Docker base image name, a local `Dockerfile` in your repository, or a public image in Docker Hub or another registry. To reference a `Dockerfile` local to your repository, the file must be named `Dockerfile` and you must use a path relative to your action metadata file. The `docker` application will execute this file.

content/rest/scim/scim.md

@@ -73,6 +73,7 @@ Name | Type | Description
 `name.familyName`|`string` | The last name of the user.
 `emails` | `array` | List of user emails.
 `externalId` | `string` | This identifier is generated by the SAML provider, and is used as a unique ID by the SAML provider to match against a GitHub user. You can find the `externalID` for a user either at the SAML provider, or using the [List SCIM provisioned identities](#list-scim-provisioned-identities) endpoint and filtering on other known attributes, such as a user's GitHub username or email address.
+`profileUrl` | `string` | The URL of the {% data variables.product.github %} account linked to the SCIM identity. This attribute is omitted when the identity is not linked to a {% data variables.product.github %} account.
 `id` | `string` | Identifier generated by the GitHub SCIM endpoint.
 `active` | `boolean` | Used to indicate whether the identity is active (true) or should be deprovisioned (false).