feat/batch-changes: document maxConcurrency batch spec field #1580
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add documentation for the new maxConcurrency field that allows batch change authors to limit how many workspace execution jobs run concurrently during server-side execution. This helps avoid overwhelming CI systems or hitting rate limits on external services. The field takes the minimum of the specified value and the instance-wide execution limit configured by site administrators. Test Plan: Verified the documentation builds locally and follows the existing style for other batch spec fields. Changelog: Added documentation for the maxConcurrency batch spec field that limits concurrent workspace executions during server-side batch changes. Amp-Thread-ID: https://ampcode.com/threads/T-019c1e9e-3f2b-700f-9000-cbda85a35e69 Co-authored-by: Amp <amp@ampcode.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
burmudar
approved these changes
Feb 2, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add documentation for the new
maxConcurrencyfield that allows batch change authors to limit how many workspace execution jobs run concurrently during server-side execution. This helps avoid overwhelming CI systems or hitting rate limits on external services.The field takes the minimum of the specified value and the instance-wide execution limit configured by site administrators.
Implements the docs side of https://github.com/sourcegraph/sourcegraph/pull/9560
Do not merge until 6.13 is released — this feature ships with that release.