You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/actions/creating-actions/creating-a-docker-container-action.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -124,7 +124,7 @@ Next, the script gets the current time and sets it as an output variable that ac
124
124
1. Make your `entrypoint.sh` file executable. Git provides a way to explicitly change the permission mode of a file so that it doesn’t get reset every time there is a clone/fork.
125
125
126
126
```shell{:copy}
127
-
$ git update-index —chmod=+x entrypoint.sh
127
+
$ git update-index --chmod=+x entrypoint.sh
128
128
```
129
129
130
130
1. Optionally, to check the permission mode of the file in the git index, run the following command.
Copy file name to clipboardExpand all lines: content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ When you use external authentication, {% data variables.product.product_location
36
36
37
37
If you use an enterprise with {% data variables.product.prodname_emus %}, members of your enterprise authenticate to access {% data variables.product.prodname_dotcom %} through your SAML identity provider (IdP). For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)" and "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)."
38
38
39
-
{% data variables.product.product_name %} automatically creates a username for each person when their user account is provisioned via SCIM, by normalizing an identifier provided by your IdP. If multiple identifiers are normalized into the same username, a username conflict occurs, and only the first user account is created. You can resolve username conflicts by making a change in your IdP so that the normalized usernames will be unique.
39
+
{% data variables.product.product_name %} automatically creates a username for each person when their user account is provisioned via SCIM, by normalizing an identifier provided by your IdP. If multiple identifiers are normalized into the same username, a username conflict occurs, and only the first user account is created. {% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %} You can resolve username conflicts by making a change in your IdP so that the normalized usernames will be unique.
Copy file name to clipboardExpand all lines: content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ By default, when an unauthenticated user attempts to access an enterprise that u
135
135
136
136
{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
137
137
138
-
A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username conflicts](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-conflicts)."
138
+
A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. {% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %} If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username conflicts](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-conflicts)."
139
139
140
140
The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address.
Copy file name to clipboardExpand all lines: content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,8 @@ If you are a site administrator for {% data variables.product.product_location %
66
66
```shell
67
67
> Generating public/private ALGORITHM key pair.
68
68
```
69
-
3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location.
69
+
When you're prompted to "Enter a file in which to save the key", you can press **Enter** to accept the default file location. Please note that if you created SSH keys previously, ssh-keygen may ask you to rewrite another key, in which case we recommend creating a custom-named SSH key. To do so, type the default file location and replace id_ssh_keyname with your custom key name.
Copy file name to clipboardExpand all lines: content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -88,15 +88,15 @@ You can download the {% data variables.product.prodname_advanced_security %} lic
88
88
{% data reusables.profile.access_org %}
89
89
{% data reusables.profile.org_settings %}
90
90
{% data reusables.organizations.billing_plans %}
91
-
1. Underneath "{% data variables.product.prodname_GH_advanced_security %}," click {% octicon "download" aria-label="The download icon" %} next to "Committers."
91
+
1. Underneath "{% data variables.product.prodname_GH_advanced_security %}," click **{% octicon "download" aria-label="The download icon" %} CSV report** next to "Committers."
92
92

93
93
94
94
#### At the enterprise-level
95
95
96
96
{% data reusables.enterprise-accounts.access-enterprise %}
97
97
{% data reusables.enterprise-accounts.settings-tab %}
98
98
{% data reusables.enterprise-accounts.license-tab %}
99
-
1. Under "{% data variables.product.prodname_GH_advanced_security %}," click {% octicon "download" aria-label="The download icon" %} next to "Commiters."
99
+
1. Under "{% data variables.product.prodname_GH_advanced_security %}," click **{% octicon "download" aria-label="The download icon" %} CSV report**next to "Committers."
100
100

101
101
102
102
### Downloading {% data variables.product.prodname_advanced_security %} license usage information through the REST API
Copy file name to clipboardExpand all lines: content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,8 @@ For general information about configuring {% data variables.product.prodname_cod
40
40
41
41
## About autobuild for {% data variables.product.prodname_codeql %}
42
42
43
-
Code scanning works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository. For the compiled languages C/C++, C#, and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
43
+
{% data variables.product.prodname_code_scanning_capc %} works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository.
44
+
For the compiled languages C/C++, C#, and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
44
45
45
46
{% data reusables.code-scanning.autobuild-compiled-languages %}
Copy file name to clipboardExpand all lines: content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,8 @@ Generally, we name our supported ecosystems after the software programming langu
Copy file name to clipboardExpand all lines: content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
+1-9
Original file line number
Diff line number
Diff line change
@@ -784,15 +784,7 @@ registries:
784
784
785
785
### `docker-registry`
786
786
787
-
{% data variables.product.prodname_dependabot %} works with container registries that implement the OCI container registry. For more information, see [https://github.com/opencontainers/distribution-spec/blob/main/spec.md](https://github.com/opencontainers/distribution-spec/blob/main/spec.md). {% data variables.product.prodname_dependabot %} supports authentication to private registries via a central service. For further details, see [Token Authentication Specification](https://docs.docker.com/registry/spec/auth/token/) in the Docker documentation.
788
-
789
-
We currently support the container registries listed here:
790
-
791
-
* Docker Hub
792
-
* {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}
793
-
* GCR (Google Cloud)
794
-
* Private ECR (AWS) - public ECR support is tracked in [https://github.com/dependabot/dependabot-core/issues/4212](https://github.com/dependabot/dependabot-core/issues/4212).
795
-
787
+
{% data variables.product.prodname_dependabot %} works with any container registries that implement the OCI container registry spec. For more information, see [https://github.com/opencontainers/distribution-spec/blob/main/spec.md](https://github.com/opencontainers/distribution-spec/blob/main/spec.md). {% data variables.product.prodname_dependabot %} supports authentication to private registries via a central token service or HTTP Basic Auth. For further details, see [Token Authentication Specification](https://docs.docker.com/registry/spec/auth/token/) in the Docker documentation and [Basic access authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) on Wikipedia.
796
788
797
789
The `docker-registry` type supports username and password.
Copy file name to clipboardExpand all lines: content/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ jobs:
61
61
go-version: ">=1.18.0"
62
62
63
63
- name: Run snapshot action
64
-
uses: @actions/go-dependency-submission@v1
64
+
uses: actions/go-dependency-submission@v1
65
65
with:
66
66
# Required: Define the repo path to the go.mod file used by the
0 commit comments