Merge pull request #8915 from github/repo-sync

repo sync

.github/workflows/sync-search-indices.yml

@@ -52,7 +52,7 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         # TODO remove version and language after first successful run to test
-        run: VERSION=github-ae@latest LANGUAGE=pt npm run sync-search
+        run: npm run sync-search
 
       - name: Update private docs repository search indexes
         # Git pre-push hooks push the LFS objects, so if you don't run them and

content/github/authenticating-to-github/troubleshooting-ssh/error-key-already-in-use.md

@@ -24,6 +24,13 @@ $ ssh -T -ai <em>~/.ssh/id_rsa</em> git@{% data variables.command_line.codeblock
 
 The *username* in the response is the {% data variables.product.product_name %} account that the key is currently attached to. If the response looks something like "username/repo", the key has been attached to a repository as a [*deploy key*](/guides/managing-deploy-keys#deploy-keys).
 
+
+To force SSH to use only the key provided on the command line, use `-o` to add the `IdentitiesOnly=yes` option:
+
+```shell
+$ ssh -v -o "IdentitiesOnly=yes" -i <em>~/.ssh/id_rsa</em> git@{% data variables.command_line.codeblock %}
+```
+
 ## Fixing the issue
 
 To resolve the issue, first remove the key from the other account or repository and then [add it to your account](/articles/adding-a-new-ssh-key-to-your-github-account).

lib/search/indexes/github-docs-ghae-pt-records.json.br

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:53fbaf8a8a8f086d4aa8e2925b219b72ba501419038f6dacfa09b6935ab3965e
-size 25491
+oid sha256:f330fd54d65f8c163190ad1fea5896af65d5e94f888f941f15ed347948929936
+size 25410

lib/search/indexes/github-docs-ghae-pt.json.br

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:434009180c715be80430eafab8ca1f8e4fb823edf5944bb6a2701f16cb3f61fc
-size 147723
+oid sha256:3b2663b66e0335e8fcb8d4684fbce5c0e8d6fb121e3e740f9b12bb00d44444a3
+size 147145