Skip to content

Commit 5f3010c

Browse files
committed
cleanup
1 parent d07d468 commit 5f3010c

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

docs/admin/config/batch_changes.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -364,10 +364,10 @@ Library examples are visible in the library pane when you are in the batch spec
364364

365365
Templates are like library examples, but with variables for easy reuse across multiple batch changes. Templates provide the simplest path for users to create batch changes without needing to learn Batch Spec YAML syntax. Users select from a curated list of templates and complete a form with the required parameters, making batch change creation accessible to all team members regardless of their technical background.
366366

367-
You can use variables to replace any text in the batch spec, allowing for flexible customization of repository queries, commands, commit messages, and more, but not for the name of the batch change.
368-
369367
A library example becomes a template once it has at least one [variable](#variables) defined. It will then be displayed on the list of templates that a user sees when they click on [create a batch change](/batch-changes/create-a-batch-change).
370368

369+
You can use variables to replace any text in the batch spec, allowing for flexible customization of repository queries, commands, commit messages, and more, but not for the name of the batch change.
370+
371371
### Managing the Batch Spec Library
372372

373373
<Callout type="note">Site admins can manage the Batch Spec library in Sourcegraph v6.4 and more.</Callout>
@@ -437,7 +437,7 @@ batchSpecLibrary(first: 100, labels: ["featured"]) {
437437

438438
Templates use variables to make batch specs adaptable to different scenarios. When creating a template, you can define placeholders for values that will vary between different uses of the template. Users filling out the template see these variables as form fields where they can enter specific values like repository names, file paths, or commit messages.
439439

440-
<Callout type="note">You cannot use a variable for the batch change or batch spec name.</Callout>
440+
<Callout type="note">You cannot use a variable for the batch change name.</Callout>
441441

442442
The `libraryVariables` field accepts an array of variable objects, each with the following configuration options:
443443

docs/batch-changes/create-a-batch-change.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ You will be redirected to a page showing you a list of curated templates.
3030
From the template selection page, you can either:
3131

3232
- **Pick a template** from the list of curated templates that best matches your use case
33-
- **Click "Create batch spec from scratch"** if you prefer to start with a blank spec
33+
- **Click "Start from Scratch"** if you prefer to start with a blank spec
3434

3535
![templates_list](https://sourcegraphstatic.com/docs/images/batch_changes/2025/templates_list.png)
3636

@@ -46,7 +46,7 @@ The form fields are validated by regular expressions. If the validation fails, l
4646

4747
### Choose a name for your batch change
4848

49-
After you've filled out the template form fields, or after you clicked "Create batch spec from scratch", you will be prompted to choose a name for your namespace and optionally define a custom namespace to put your batch change in.
49+
After you've filled out the template form fields, or after you clicked "Start from Scratch", you will be prompted to choose a name for your namespace and optionally define a custom namespace to put your batch change in.
5050

5151
![server-side-batch-change](https://sourcegraphstatic.com/docs/images/batch_changes/2024/create-a-batch-change.png)
5252

0 commit comments

Comments
 (0)