Skip to content

fix: add missing word #832

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 4, 2024
Merged

fix: add missing word #832

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/batch-changes/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ However, if the user deletion is permanent (using the "Delete forever" option),
## Are there any limitations with the Batch Changes feature?

- **Code hosts**: Batch Changes currently support **GitHub**, **GitLab** and **Bitbucket Server and Bitbucket Data Center** repositories. If you want to use Batch Changes on other code hosts, [let us know](https://about.sourcegraph.com/contact).
- **Server-side execution**: Batch change steps are run locally (in the [Sourcegraph CLI](https://github.com/sourcegraph/src-cli)) or [server-side](/batch-changes/server-side) `Beta`. For this reason, the APIs for creating and updating a batch change require you to upload all of the changeset specs (which are produced by executing the batch spec locally). Also, see [how scalable Batch Changes](/batch-changes/faq#how-scalable-are-batch-changes-how-many-changesets-can-i-create).
- **Server-side execution**: Batch change steps are run locally (in the [Sourcegraph CLI](https://github.com/sourcegraph/src-cli)) or [server-side](/batch-changes/server-side) `Beta`. For this reason, the APIs for creating and updating a batch change require you to upload all of the changeset specs (which are produced by executing the batch spec locally). Also, see [how scalable Batch Changes are](/batch-changes/faq#how-scalable-are-batch-changes-how-many-changesets-can-i-create).
- **Multi-user access**: It is yet to be possible for multiple users to edit the same batch change that was created under an organization.
- It is yet to be possible to reuse a branch in a repository across multiple batch changes.
- The only type of user credential supported by Sourcegraph right now is a [personal access token](/batch-changes/configuring-credentials), either per user, or via a global service account. Further credential types may be supported in the future.
Expand Down
Loading