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: docs/batch-changes/create-a-batch-change.mdx
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
3
3
<pclassName="subtitle">Learn in detail about how to create, view, and filter your Batch Changes.</p>
4
4
5
-
Batch changes are created by writing a [batch spec](/batch-changes/batch-spec-yaml-reference) and executing that batch spec with the [Sourcegraph CLI](https://github.com/sourcegraph/src-cli)`src`.
5
+
Batch Changes are created by writing a [batch spec](/batch-changes/batch-spec-yaml-reference) and executing that batch spec with the [Sourcegraph CLI](https://github.com/sourcegraph/src-cli)`src`.
6
6
7
-
Batch changes can also be used on [multiple projects within a monorepo](/batch-changes/creating-changesets-per-project-in-monorepos) by using the `workspaces` key in your batch spec.
7
+
Batch Changes can also be used on [multiple projects within a monorepo](/batch-changes/creating-changesets-per-project-in-monorepos) by using the `workspaces` key in your batch spec.
8
8
9
-
There are two ways of creating a Batch Change:
9
+
There are two ways of creating a batch change:
10
10
11
11
1. On your local machine, with the [Sourcegraph CLI](#create-a-batch-change-with-the-sourcegraph-cli)
12
12
2. Remotely, with [server-side execution](/batch-changes/server-side)
@@ -23,7 +23,7 @@ This part of the guide will walk you through creating a batch change on your loc
23
23
24
24
### Writing a batch spec
25
25
26
-
To create a Batch Change, you need a **batch spec** describing the change. Here is an example batch spec that describes a batch change to add **Hello World** to all `README` files:
26
+
To create a batch change, you need a **batch spec** describing the change. Here is an example batch spec that describes a batch change to add **Hello World** to all `README` files:
27
27
28
28
```yaml
29
29
version: 2
@@ -105,9 +105,9 @@ That can be useful if you want to update a single field in the batch spec, i.e.,
105
105
106
106
### Creating a batch change in a different namespace
107
107
108
-
Batch changes are uniquely identified by their name and namespace. The namespace can be any Sourcegraph username or the name of a Sourcegraph organization.
108
+
Batch Changes are uniquely identified by their name and namespace. The namespace can be any Sourcegraph username or the name of a Sourcegraph organization.
109
109
110
-
By default, batch changes will use your username on Sourcegraph as your namespace. To create batch changes in a different namespace, use the `-namespace` flag when previewing or applying a batch spec:
110
+
By default, Batch Changes will use your username on Sourcegraph as your namespace. To create Batch Changes in a different namespace, use the `-namespace` flag when previewing or applying a batch spec:
There is a drop-down menu for Cody's suggestions mode. You can choose between the default autocomplete and the auto-edit mode, or you can turn off the suggestions completely.
31
36
32
37
The following example demonstrates how to add Fireworks as an allowed LLM provider:
33
38
@@ -40,7 +45,7 @@ The following example demonstrates how to add Fireworks as an allowed LLM provid
40
45
// Only allow "beta" and "stable" models.
41
46
// Not "experimental" or "deprecated".
42
47
"statusFilter": ["beta", "stable"],
43
-
48
+
44
49
// Allow any models provided by Anthropic, OpenAI, Google and Fireworks.
Copy file name to clipboardExpand all lines: docs/cody/capabilities/supported-models.mdx
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -43,4 +43,6 @@ Cody uses a set of models for autocomplete which are suited for the low latency
43
43
44
44
<Callouttype="note">The default autocomplete model for Cody Free, Pro and Enterprise users is DeepSeek-Coder-V2.</Callout>
45
45
46
+
<Callouttype="note">The DeepSeek model used by Sourcegraph is hosted by Fireworks.ai, and is hosted as a single-tenant service in a US-based data center. For more information see our [Cody FAQ](https://sourcegraph.com/docs/cody/faq#is-any-of-my-data-sent-to-deepseek).</Callout>
47
+
46
48
Read here for [Ollama setup instructions](https://sourcegraph.com/docs/cody/clients/install-vscode#supported-local-ollama-models-with-cody). For information on context token limits, see our [documentation here](/cody/core-concepts/token-limits).
Copy file name to clipboardExpand all lines: docs/cody/faq.mdx
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -100,6 +100,14 @@ Cody does not support embeddings on Cody PLG and Cody Enterprise because we have
100
100
101
101
Leveraging Sourcegraph Search allowed us to deliver these enhancements.
102
102
103
+
## LLM Data Sharing and Retention
104
+
105
+
### Is any of my data sent to DeepSeek?
106
+
107
+
Our autocomplete features uses the open source DeepSeek-Coder-V2 model, which is hosted by Fireworks.ai in a secure single-tenant environment located in the USA. No customer chat or autocomplete data - such as chat messages, or context such as code snippets or configuration - is stored by Fireworks.ai.
108
+
109
+
Sourcegraph does not use models hosted by DeepSeek (the company), and does not send any data to the same.
110
+
103
111
## Third party dependencies
104
112
105
113
### What is the default `sourcegraph` provider for completions?
Copy file name to clipboardExpand all lines: docs/cody/troubleshooting.mdx
+14Lines changed: 14 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -105,6 +105,20 @@ It indicates that our web application firewall provider, Cloudflare, has flagged
105
105
106
106
Consider disabling anonymizers, VPNs, or open proxies. If using a VPN is essential, you can try [1.1.1.1](https://one.one.one.one), which is recognized to be compatible with our services.
107
107
108
+
### Error with Cody `contextFilters` during chat or editing code
109
+
110
+
The `contextFilters` setting in Cody is used to control which files are included or excluded when Cody searches for relevant context while answering questions or providing code assistance. Sometimes, you can see the following error:
111
+
112
+
```
113
+
Edit failed to run: file is ignored (due to cody.contextFilters Enterprise configuration setting)
114
+
```
115
+
116
+
This error occurs when you're trying to work with a file that's been excluded by Cody's enterprise-level `contextFilters` configuration. At times, this can happen to files that also haven't been excluded. First, check with your organization's admin to understand which files are excluded.
117
+
118
+
If the error occurs with a file that's not been excluded, the workaround is to uninstall the Cody plugin, restart your IDE and then reinstall the latest version of the extension.
119
+
120
+
This should clear the error.
121
+
108
122
### VS Code Pro License Issues
109
123
110
124
If VS Code prompts you to upgrade to Pro despite already having a Pro license, this usually happens because you're logged into a free Cody/Sourcegraph account rather than your Pro account. To fix this:
0 commit comments