Merge branch 'main' into hackathon-faq

Author: MaedahBatool

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/monorepo.mdx

@@ -27,12 +27,12 @@ Some monorepos use a custom command for `git fetch` to speed up fetch. Sourcegra
 
 ## Statistics
 
-You can help the Sourcegraph developers understand the scale of your monorepo by sharing some statistics with the team. The bash script [`git-stats`](https://github.com/sourcegraph/sourcegraph/blob/main/dev/git-stats) when run in your git repository will calculate these statistics.
+You can help the Sourcegraph developers understand the scale of your monorepo by sharing some statistics with the team. The bash script [`git-stats`](https://github.com/sourcegraph/sourcegraph-public-snapshot/blob/main/dev/git-stats) when run in your git repository will calculate these statistics.
 
 Example output on the Sourcegraph repository:
 
 ``` shellsession
-$ wget https://github.com/sourcegraph/sourcegraph/raw/main/dev/git-stats
+$ wget https://github.com/sourcegraph/sourcegraph-public-snapshot/raw/main/dev/git-stats
 $ chmod +x git-stats
 $ ./git-stats
 725M	. gitdir

docs/code-search/queries/index.mdx

@@ -38,7 +38,7 @@ Clicking the (.*) toggle interprets all search patterns as regular expressions.
 | [`foo bar`](https://sourcegraph.com/search?q=context:global+repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+foo+bar&patternType=regexp)                     | Search for the regexp `foo(.*?)bar`. Spaces between non-whitespace strings becomes `.*?` to create a fuzzy search                                                                                          |
 | [`foo\ bar`](https://sourcegraph.com/search?q=foo%5C+bar&patternType=regexp) or [`/foo bar/`](https://sourcegraph.com/search?q=/foo+bar/&patternType=regexp) | Search for the regexp `foo bar`. The `\` escapes the space and treats the space as part of the pattern. Use `/.../` to avoid escaping spaces                                            |
 | [`foo\nbar`](https://sourcegraph.com/search?q=foo%5Cnbar&patternType=regexp)                                                                                 | Perform a multiline regexp search. `\n` is interpreted as a newline                                                                                                                                        |
-| [`"foo bar"`](https://sourcegraph.com/search?q=%27foo+bar%27&patternType=regexp)                                                                             | Match the string literal `"foo bar"`. Quotes interpret strings exactly, except that special characters like `"` and `\` may be escaped, and whitespace escape sequences like `\n` are interpreted normally |
+| [`"foo bar"`](https://sourcegraph.com/search?q=%22foo+bar%22&patternType=regexp)                                                                             | Match the string `foo bar` exactly. The space between the terms is interpreted literally. The quotes are not matched.                                                                |
 
 <Callout type="note">We support [RE2 syntax](https://golang.org/s/re2syntax). Matching is case-insensitive by default (toggle the `Aa` button to change).</Callout>
 

docs/cody/capabilities/chat.mdx

@@ -4,7 +4,7 @@
 
 You can **chat** with Cody to ask questions about your code, generate code, and edit code. By default, Cody has the context of your open file and entire repository, and you can use `@` to add context for specific files, symbols, remote repositories, or other non-code artifacts.
 
-You can do it from the **chat** panel of the supported editor extensions ([VS Code](/clients/install-vscode), [JetBrains](/clients/install-jetbrains), [Visual Studio](/clients/install-visual-studio)) or in the [web](/clients/cody-with-sourcegraph) app.
+You can do it from the **chat** panel of the supported editor extensions ([VS Code](/cody/clients/install-vscode), [JetBrains](/cody/clients/install-jetbrains), [Visual Studio](/cody/clients/install-visual-studio)) or in the [web](/cody/clients/cody-with-sourcegraph) app.
 
 ## Prerequisites
 

docs/cody/capabilities/openctx.mdx

@@ -6,11 +6,13 @@
 
 [OpenCtx](https://openctx.org/) is an open standard for bringing contextual info about code into your dev tools. Cody Free and Pro users can use OpenCtx providers to fetch and use context from the following sources:
 
-- [Webpages](https://openctx.org/docs/providers/web) (via URL)
+- [Webpages (via URL)](https://openctx.org/docs/providers/web) (enabled in Cody by default)
 - [Jira tickets](https://openctx.org/docs/providers/jira)
 - [Linear issues](https://openctx.org/docs/providers/linear-issues)
 - [Notion pages](https://openctx.org/docs/providers/notion)
 - [Google Docs](https://openctx.org/docs/providers/google-docs)
+- [Slack](https://openctx.org/docs/providers/slack)
+- [Storybook](https://openctx.org/docs/providers/storybook)
 - [Sourcegraph code search](https://openctx.org/docs/providers/sourcegraph-search)
 
 ## Enable OpenCtx context providers

docs/cody/clients/cody-with-sourcegraph.mdx

@@ -29,11 +29,11 @@ The chat interface with your Code Search queries is operated per chat. You canno
 
 ## LLM Selection
 
-Sourcegraph.com users with Cody **Free** and **Pro** can choose from a list of supported LLM models for a chat. Claude Sonnet 3.5 is the default LLM model, but users can select the LLM of their choice from the drop-down menu.
+Cody Free and Pro users can select multiple models. Enterprise users with the new [model configuration](/cody/clients/model-configuration) can use the LLM selection dropdown to choose a chat model.
 
-![llm-select-web](https://storage.googleapis.com/sourcegraph-assets/Docs/llm-select-web-0724.jpg)
+You can read about these supported LLM models [here](/cody/capabilities/supported-models#chat-and-commands).
 
-Users on an Enterprise Sourcegraph instance do not have the option to choose an LLM model. Their site admin will configure the default LLM model for chat. However, Enterprise users with the new [model configuration](/cody/clients/model-configuration) can use the LLM selection dropdown to choose a chat model.
+![LLM-models-for-cody-free](https://storage.googleapis.com/sourcegraph-assets/Docs/llm-dropdown-options-102024.png)
 
 ## Selecting Context with @-mentions
 

docs/cody/clients/index.mdx

@@ -1,10 +1,11 @@
 # Cody Clients
 
-<p className="subtitle">You can install and start using Cody in your favorite IDEs and with the Sourcegraph web app.</p>
+<p className="subtitle">There are multiple ways to use Cody: you can install its extension in your favorite IDEs, access it via the Sourcegraph web app, or use it through the Cody CLI.</p>
 
 <ProductCards>
 <ProductCard href="/cody/clients/install-vscode" imgSrc="https://storage.googleapis.com/sourcegraph-assets/docs/images/cody/vscode.svg" imgAlt="VS Code" title="Cody for VS Code" description="Install Cody's free extension for VS Code. " />
 <ProductCard href="/cody/clients/install-jetbrains" imgSrc="https://storage.googleapis.com/sourcegraph-assets/docs/images/cody/jb_beam.svg" imgAlt="JetBrains" title="Cody for JetBrains" description="Install Cody's free extension for JetBrains." />
+<ProductCard href="/cody/clients/install-visual-studio" imgSrc="https://storage.googleapis.com/sourcegraph-assets/Docs/visual-studio-Product-Icon.svg" imgAlt="Visual Studio" title="Cody for Visual Studio (Experimental)" description="Install Cody's free extension for Visual Studio." />
 <ProductCard href="/cody/clients/cody-with-sourcegraph" imgSrc="https://storage.googleapis.com/sourcegraph-assets/docs/images/cody/cody-logomark-default.svg" imgAlt="Cody Web" title="Cody for Web" description="Use Cody in the Sourcegraph web app." />
 <ProductCard href="/cody/clients/install-cli" imgSrc="https://storage.googleapis.com/sourcegraph-assets/docs/images/cody/command-line-blue.svg" imgAlt="Cody CLI" title="Cody CLI" description="Run Cody from the command line." />
 <ProductCard href="/cody/clients/enable-cody-enterprise" imgSrc="https://sourcegraph.com/.assets/img/sourcegraph-mark.svg" imgAlt="Cody Enterprise" title="Cody Enterprise" description="Get in touch with our team to try Cody for Sourcegraph Enterprise." />