Merge branch 'main' into hackathon-cody-visual-studio

Author: MaedahBatool

README.md

@@ -1,6 +1,6 @@
 # Sourcegraph Docs
 
-<!-- Working branch for October 30th 2024 Release -->
+<!-- Working branch for Nov 25th 2024 Release -->
 
 Welcome to the Sourcegraph documentation! We're excited to have you contribute to our docs. We've recently rearchitectured our docs tech stack — powered by Next.js, TailwindCSS and deployed on Vercel. This guide will walk you through the process of contributing to our documentation using the new tech stack.
 
@@ -148,7 +148,7 @@ As you make changes to the documentation, the development server will automatica
 
 ### Previewing Vercel Deployments
 
-When you open a PR Vercel deploys and provides you with a preview deployment link. To view your deployment, click the "Visit Preview" and then append `/docs` at the end of the URL. The original link gives you a `404`. 
+When you open a PR Vercel deploys and provides you with a preview deployment link. To view your deployment, click the "Visit Preview" and then append `/docs` at the end of the URL. The original link gives you a `404`.
 
 ![CleanShot 2024-11-05 at 10 11 29@2x](https://github.com/user-attachments/assets/b0911e2e-95a7-4f56-b2ff-b659d13077d8)
 

baseai/memory/docs/index.ts

@@ -5,10 +5,9 @@ const memoryDocs = (): MemoryI => ({
   name: 'docs',
   description: 'Docs folder of sourcegraph docs repository as an auto-synced memory',
   config: {
-    deployedCommitHash: '7a147cfb18f19d5584ffb3805b678db47191960a',
-		useGitRepo: true,
-		dirToTrack: path.posix.join('.', 'docs'),
-		extToTrack: [".md",".mdx"]
+    useGitRepo: true,
+    dirToTrack: path.posix.join('.', 'docs'),
+    extToTrack: [".md", ".mdx"]
   }
 });
 

docs.config.js

@@ -1,5 +1,5 @@
 const config = {
-	DOCS_LATEST_VERSION: '5.9'
+	DOCS_LATEST_VERSION: '5.10'
 };
 
 module.exports = config;

docs/admin/auth/builtin.mdx

@@ -57,6 +57,8 @@ New users can submit a form and site admins will see the request in the navbar o
 
 ![List of pending access requests for admin to approve](https://storage.googleapis.com/sourcegraph-assets/docs/images/admin/auth/pending-access-requests.png)
 
+## Disable account requests from users
+
 The account request feature can be disabled by setting `"auth.accessRequest": { "enabled": false }`. When disabled, new user accounts can only be created by the site admin manually.
 
 ## Creating builtin authentication users

docs/admin/code_hosts/github.mdx

@@ -220,6 +220,8 @@ When creating your fine-grained access token, select the following permissions d
 
 To clone and search private repositories, we need [a GitHub access token](#github-api-access) with the required scopes and at least read access to the relevant private repositories.
 
+<Callout type="note">Due to GitHub limitations, non-admins of an outside organization must use a [Classic personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#types-of-personal-access-tokens) to provision the appropriate permissions for Sourcegraph to index that organization's private repositories.</Callout>
+
 For more details, see [GitHub API access](#github-api-access).
 
 ## Selecting repositories to sync

docs/admin/code_hosts/go.mdx

@@ -28,7 +28,7 @@ Each entry in the `"urls"` array can contain basic auth if needed (e.g. `https:/
 ## Rate limiting
 
 By default, requests to the Go module proxies will be rate-limited
-based on a default internal limit. ([source](https://github.com/sourcegraph/sourcegraph/blob/main/schema/go-modules.schema.json))
+based on a default internal limit. ([source](https://github.com/sourcegraph/sourcegraph-public-snapshot/blob/main/schema/go-modules.schema.json))
 
 ```json
 "rateLimit": {

docs/admin/code_hosts/non-git.mdx

@@ -114,4 +114,4 @@ For more complex setups, configure your `src-expose` by providing a local config
 src-expose -snapshot-config config.yaml
 ```
 
-See [an example YAML file containing available configuration options](https://github.com/sourcegraph/sourcegraph/blob/main/dev/src-expose/examples/example.yaml).
+See [an example YAML file containing available configuration options](https://github.com/sourcegraph/sourcegraph-public-snapshot/blob/main/dev/src-expose/examples/example.yaml).

docs/admin/config/private-network.mdx

@@ -4,11 +4,12 @@ A **private network** refers to a secure network environment segregated from the
 When deploying self-hosted Sourcegraph instances in private networks with specific compliance and policy requirements, additional configuration may be required to ensure all networking features function correctly. The reasons for applying the following configuration options depend on the specific functionality of the Sourcegraph service and the unique network and infrastructure requirements of the organization. 
 
 The following is a list of Sourcegraph services and how and when each initiates outbound connections to external services:
+- **executor**: Sourcegraph [Executor](../executors) batch change or precise indexing jobs may need to connect to services hosted within an organization's private network
 - **frontend**: The frontend service communicates externally when connecting to external [auth providers](../auth), sending [telemetry data](../pings), testing code host connections, and connecting to [externally hosted](../external_services) Sourcegraph services
 - **gitserver**: Executes git commands against externally hosted [code hosts](../external_service)
-- **repo-updater**: Communicates with [code hosts](../external_service) APIs to coordinate repository synchronization
 - **migrator**: Connects to Postgres instances (which may be [externally hosted](../external_services/postgres)) to process database migrations
-- **executor**: Sourcegraph [Executor](../executors) batch change or precise indexing jobs may need to connect to services hosted within an organization's private network
+- **repo-updater**: Communicates with [code hosts](../external_service) APIs to coordinate repository synchronization
+- **worker**: Sourcegraph [Worker](../workers) run various background jobs that may require establishing connections to services hosted within an organization's private network
 
 ## HTTP proxy configuration
 All Sourcegraph services respect the conventional `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables for routing Sourcegraph client application HTTP traffic through a proxy server. The steps for configuring proxy environment variables will depend on your Sourcegraph deployment method.
@@ -17,14 +18,14 @@ All Sourcegraph services respect the conventional `HTTP_PROXY`, `HTTPS_PROXY`, a
 Add the proxy environment variables to your Sourcegraph Helm chart [override file](https://github.com/sourcegraph/deploy-sourcegraph-helm/blob/main/charts/sourcegraph/values.yaml):
 
 ```yaml
-frontend|gitserver|repo-updater:
+executor|frontend|gitserver|migrator|repo-updater|worker:
   env:
   - name: HTTP_PROXY 
     value: http://proxy.example.com:8080
   - name: HTTPS_PROXY
     value: http://proxy.example.com:8080
   - name: NO_PROXY
-    value:  "*.cluster.local,blobstore,codeinsights-db,codeintel-db,sourcegraph-frontend-internal,sourcegraph-frontend,github-proxy,gitserver,grafana,indexed-search-indexer,indexed-search,jaeger-query,pgsql,precise-code-intel-worker,prometheus,redis-cache,redis-store,repo-updater,searcher,symbols,syntect-server,worker-executors,worker" 
+    value: "blobstore,codeinsights-db,codeintel-db,sourcegraph-frontend-internal,sourcegraph-frontend,github-proxy,gitserver,grafana,indexed-search-indexer,indexed-search,jaeger-query,pgsql,precise-code-intel-worker,prometheus,redis-cache,redis-store,repo-updater,searcher,symbols,syntect-server,worker-executors,worker,cloud-sql-proxy,localhost,127.0.0.1,.svc,.svc.cluster.local,kubernetes.default.svc"
 ```
 
 <Callout type="warning">Failure to configure `NO_PROXY` correctly can cause the proxy configuration to interfere with local networking between internal Sourcegraph services.</Callout>

docs/admin/deploy/kubernetes/index.mdx

@@ -1105,7 +1105,7 @@ Some Persistent Volumes may be retained after the uninstall phase is complete. I
 [AWS EBS CSI driver]: https://docs.aws.amazon.com/eks/latest/userguide/managing-ebs-csi.html
 [NGINX Ingress Controller]: https://github.com/kubernetes/ingress-nginx
 [Helm Changelog]: https://github.com/sourcegraph/deploy-sourcegraph-helm/blob/main/charts/sourcegraph/CHANGELOG
-[Sourcegraph Changelog]: https://github.com/sourcegraph/sourcegraph/blob/main/CHANGELOG
+[Sourcegraph Changelog]: https://github.com/sourcegraph/sourcegraph-public-snapshot/blob/main/CHANGELOG
 [Sourcegraph Migrator]: https://github.com/sourcegraph/deploy-sourcegraph-helm/blob/main/charts/sourcegraph-migrator
 [Helm Diff]: https://github.com/databus23/helm-diff
 [Secrets]: https://kubernetes.io/docs/concepts/configuration/secret/

docs/admin/executors/deploy_executors_terraform.mdx

@@ -410,7 +410,7 @@ Next, you can test whether the number of executors rises and shrinks as load spi
 ## Upgrading executors
 
 Upgrading executors is relatively uninvolved. Simply follow the instructions below.
-Also, check the [changelog](https://github.com/sourcegraph/sourcegraph/blob/main/CHANGELOG) for any Executors related breaking changes or new features or flags that you might want to configure. See [Executors maintenance](/admin/executors/deploy_executors#Maintaining-and-upgrading-executors) for version compatability.
+Also, check the [changelog](https://github.com/sourcegraph/sourcegraph-public-snapshot/blob/main/CHANGELOG) for any Executors related breaking changes or new features or flags that you might want to configure. See [Executors maintenance](/admin/executors/deploy_executors#Maintaining-and-upgrading-executors) for version compatability.
 
 ### **Step 1:** Update the source version of the terraform modules