Repo sync

content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-azure.md

@@ -77,7 +77,6 @@ The [`azure/login`](https://github.com/Azure/login) action receives a JWT from t
 
 The following example exchanges an OIDC ID token with Azure to receive an access token, which can then be used to access cloud resources.
 
-
 ```yaml copy
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 name: Run Azure Login with OIDC
@@ -93,9 +92,9 @@ jobs:
       - name: 'Az CLI login'
         uses: azure/login@8c334a195cbb38e46038007b304988d888bf676a
         with:
-          client-id: ${{ secrets.AZURE_CLIENT_ID }}
-          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
-          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
+          client-id: {% raw %}${{ secrets.AZURE_CLIENT_ID }}{% endraw %}
+          tenant-id: {% raw %}${{ secrets.AZURE_TENANT_ID }}{% endraw %}
+          subscription-id: {% raw %}${{ secrets.AZURE_SUBSCRIPTION_ID }}{% endraw %}
 
       - name: 'Run az commands'
         run: |

content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-google-cloud-platform.md

@@ -103,7 +103,7 @@ jobs:
     - id: 'gcloud'
       name: 'gcloud'
       run: |-
-        gcloud auth login --brief --cred-file="${{ steps.auth.outputs.credentials_file_path }}"
+        gcloud auth login --brief --cred-file="{% raw %}${{ steps.auth.outputs.credentials_file_path }}{% endraw %}"
         gcloud services list
 ```
 

content/actions/how-tos/secure-your-work/security-harden-deployments/oidc-in-jfrog.md

@@ -69,7 +69,7 @@ jobs:
         id: setup-jfrog-cli
         uses: jfrog/setup-jfrog-cli@29fa5190a4123350e81e2a2e8d803b2a27fed15e
         with:
-          JF_URL: ${{ env.JF_URL }}
+          JF_URL: {% raw %}${{ env.JF_URL }}{% endraw %}
           oidc-provider-name: 'YOUR_PROVIDER_NAME'
           oidc-audience: 'YOUR_AUDIENCE' # This is optional
 
@@ -85,20 +85,16 @@ jobs:
 
 ### Using OIDC Credentials in other steps
 
-{% raw %}
-
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
       - name: Sign in to Artifactory Docker registry
         uses: docker/login-action@v3
         with:
-          registry: ${{ env.JF_URL }}
-          username: ${{ steps.setup-jfrog-cli.outputs.oidc-user }}
-          password: ${{ steps.setup-jfrog-cli.outputs.oidc-token }}
+          registry: {% raw %}${{ env.JF_URL }}{% endraw %}
+          username: {% raw %}${{ steps.setup-jfrog-cli.outputs.oidc-user }}{% endraw %}
+          password: {% raw %}${{ steps.setup-jfrog-cli.outputs.oidc-token }}{% endraw %}
 ```
 
-{% endraw %}
-
 ## Further reading
 
 * [OpenID Connect Integration](https://jfrog.com/help/r/jfrog-platform-administration-documentation/openid-connect-integration) in the JFrog documentation

content/actions/tutorials/build-and-test-code/ruby.md

@@ -187,8 +187,6 @@ The `setup-ruby` actions provides a method to automatically handle the caching o
 
 To enable caching, set the following.
 
-{% raw %}
-
 ```yaml
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 steps:
@@ -197,8 +195,6 @@ steps:
     bundler-cache: true
 ```
 
-{% endraw %}
-
 This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by {% data variables.product.prodname_actions %} and re-downloaded for subsequent workflow runs. A hash of your `gemfile.lock` and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install.
 
 **Caching without setup-ruby**

content/actions/tutorials/build-and-test-code/swift.md

@@ -124,8 +124,6 @@ jobs:
 
 You can configure your job to use a single specific version of Swift, such as `5.3.3`.
 
-{% raw %}
-
 ```yaml copy
 {% data reusables.actions.actions-not-certified-by-github-comment %}
 steps:
@@ -136,8 +134,6 @@ steps:
     run: swift --version # Swift 5.3.3
 ```
 
-{% endraw %}
-
 ## Building and testing your code
 
 You can use the same commands that you use locally to build and test your code using Swift. This example demonstrates how to use `swift build` and `swift test` in a job:

content/admin/data-residency/network-details-for-ghecom.md

@@ -33,6 +33,7 @@ For more information, see [AUTOTITLE](/rest/meta/meta).
 * `*.githubassets.com`
 * `*.githubusercontent.com`
 * `*.blob.core.windows.net`
+* `auth.ghe.com`
 
 ## {% data variables.product.github %}'s IP addresses
 

content/code-security/concepts/supply-chain-security/about-the-dependency-graph.md

@@ -60,9 +60,23 @@ For more information on how {% data variables.product.github %} helps you unders
 
 {% ifversion fpt or ghec %}
 
-## Dependents included
+## Dependents and "used by" data
 
-For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
+For public repositories, the dependency graph lists dependents. These are other public repositories that depend on the repository or on packages that it publishes. This information is not reported for private repositories.
+
+{% data reusables.dependency-graph.used-by %} Clicking any item in this section takes you to the **Dependents** tab of the dependency graph.
+
+Your repository will have a "Used by" section if:
+* The dependency graph is enabled for the repository.
+* Your repository contains a package that is published on a supported package ecosystem. See [AUTOTITLE](/code-security/supply-chain-security/understanding-your-software-supply-chain/dependency-graph-supported-package-ecosystems#supported-package-ecosystems).
+* Within the ecosystem, your package has a link to a _public_ repository where the source is stored.
+* More than 100 repositories depend on your package.
+
+![Screenshot of the "Used by" section for a repository showing the summary of "13.4m" with details of 8 avatars and "+13,435,819."](/assets/images/help/repository/used-by-section.png)
+
+The "Used by" section represents a single package from the repository. If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents. See [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/change-used-by-data).
+
+{% endif %}
 
 ## What you can do with the dependency graph
 

content/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/exploring-the-dependencies-of-a-repository.md

@@ -81,31 +81,6 @@ If vulnerabilities have been detected in the repository, these are shown at the
 
 For public repositories, the dependents view shows how the repository is used by other repositories. To show only the repositories that contain a library in a package manager, click **NUMBER Packages** immediately above the list of dependent repositories. The dependent counts are approximate and may not always match the dependents listed.
 
-## Enabling and disabling the dependency graph
-
-{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo-public-fork %}
-
-## Changing the "Used by" package
-
-You may notice some repositories have a "Used by" section in the sidebar of the **Code** tab. Your repository will have a "Used by" section if:
-* The dependency graph is enabled for the repository (see the above section for more details).
-* Your repository contains a package that is published on a [supported package ecosystem](/code-security/supply-chain-security/understanding-your-software-supply-chain/dependency-graph-supported-package-ecosystems#supported-package-ecosystems).
-* Within the ecosystem, your package has a link to a _public_ repository where the source is stored.
-* More than 100 repositories depend on your package.
-
-The "Used by" section shows the number of public references to the package that were found, and displays the avatars of some of the owners of the dependent projects.
-
-![Screenshot of the "Used by" section for a repository showing the summary of "13.4m" with details of 8 avatars and "+13,435,819."](/assets/images/help/repository/used-by-section.png)
-
-Clicking any item in this section takes you to the **Dependents** tab of the dependency graph.
-
-The "Used by" section represents a single package from the repository. If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents.
-
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-code-security-and-analysis %}
-1. Under "{% data variables.product.UI_advanced_security %}", click the drop-down menu in the "Used by counter" section and choose a package.
-
 {% endif %}
 
 ## Further reading

content/code-security/how-tos/view-and-interpret-data/change-used-by-data.md

@@ -0,0 +1,19 @@
+---
+title: Changing the "used by" data for a repository
+shortTitle: Change "used by" data
+intro: Display your repository's dependents for a different package.
+permissions: 'Repository administrators'
+versions:
+  fpt: '*'
+  ghec: '*'
+contentType: how-tos
+---
+
+{% data reusables.dependency-graph.used-by %} For more information, see [AUTOTITLE](/code-security/concepts/supply-chain-security/about-the-dependency-graph#dependents-and-used-by-data).
+
+If you have admin permissions to a repository that contains multiple packages, you can choose which package the "Used by" section represents.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+1. Under "{% data variables.product.UI_advanced_security %}", click the drop-down menu in the "Used by counter" section and choose a package.

content/code-security/how-tos/view-and-interpret-data/index.md

@@ -20,4 +20,5 @@ children:
   - /viewing-code-scanning-logs
   - /viewing-dependabot-job-logs
   - /metrics-for-custom-patterns
+  - /change-used-by-data
 ---

data/reusables/dependency-graph/used-by.md

@@ -0,0 +1 @@
+Some repositories have a "Used by" section in the sidebar of the **Code** tab. This section shows the number of public references to a package that were found, and displays the avatars of some of the owners of the dependent projects.