Skip to content

Commit ad419ba

Browse files
authored
Merge branch 'main' into loc-file-counts
2 parents b8aafdc + f9a53fb commit ad419ba

File tree

2 files changed

+41
-1
lines changed

2 files changed

+41
-1
lines changed

docs/admin/config/batch_changes.mdx

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -370,3 +370,42 @@ batchSpecLibrary(first: 100) {
370370
}
371371
}
372372
```
373+
374+
### Featured Templates
375+
376+
<Callout type="note">Featured templates are supported in Sourcegraph v6.4 and more.</Callout>
377+
378+
Site-admins can mark a template as featured by either clicking the star button next to the list of library records. Featured records will automatically move to a section atop the remaining library records.
379+
380+
### Labels
381+
382+
<Callout type="note">Labels are supported in Sourcegraph v6.4 and more.</Callout>
383+
384+
Batch Spec Library records support an optional `labels` field for categorization and filtering. Common labels include:
385+
386+
- `"featured"` - Marks popular or recommended batch specs that are displayed in a "Featured Templates" section above the remaining examples
387+
- Custom labels for organizational categorization (not exposed to Batch Changes users yet)
388+
389+
To remove the featured status, you can update the library record with an empty list of labels (`[]`).
390+
391+
```graphql
392+
createBatchSpecLibraryRecord(name: "example", spec: "version: 2\nname: example", labels: ["featured"]) {
393+
id
394+
labels
395+
}
396+
397+
updateBatchSpecLibraryRecord(id: "QmF0Y2hTcGVjTGlicmFyeVJlY29yZDo4", name: "example-2", spec: "version: 2\nname: example-2", labels: ["featured"]) {
398+
id
399+
labels
400+
}
401+
402+
# Query only featured batch specs
403+
batchSpecLibrary(first: 100, labels: ["featured"]) {
404+
nodes {
405+
id
406+
name
407+
labels
408+
spec
409+
}
410+
}
411+
```

docs/batch-changes/bulk-operations-on-changesets.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,11 +33,12 @@ Below is a list of supported bulk operations for changesets and the conditions w
3333
| **Commenting** | Post a comment on all selected changesets. Useful for pinging people, reminding them to take a look at the changeset, or posting your favorite emoji |
3434
| **Detach** | Detach a selection of changesets from the batch change to remove them from the archived tab |
3535
| **Re-enqueue** | Re-enqueues the pending changes for all selected changesets that failed |
36-
| **Merge (experimental)** | Merge the selected changesets on code hosts. Some changesets may be unmergeable due to their states, which does not impact the overall bulk operation. Failed merges are listed under the bulk operations tab. In the confirmation modal, you can opt for a squash merge strategy, available on GitHub, GitLab, and Bitbucket Cloud. For Bitbucket Server/Data Center, only regular merges are performed |
36+
| **Merge** | Merge the selected changesets on code hosts. Some changesets may be unmergeable due to their states, which does not impact the overall bulk operation. Failed merges are listed under the bulk operations tab. In the confirmation modal, you can opt for a squash merge strategy, available on GitHub, GitLab, and Bitbucket Cloud. For Bitbucket Server/Data Center, only regular merges are performed |
3737
| **Close** | Close the selected changesets on the code hosts |
3838
| **Publish** | Publishes the selected changesets, provided they don't have a [`published` field](/batch-changes/batch-spec-yaml-reference#changesettemplatepublished) in the batch spec. You can choose between draft and normal changesets in the confirmation modal |
3939
| **Export** | Export selected changesets that you can use for later use |
4040
| **Re-execute** | Users can re-execute individual changeset creation logic for selected workspaces. This allows for creating new changesets for users who are using non-deterministic run steps (for example,LLMs) |
41+
| **Enable auto-merge for GitHub (experimental)** | Enable auto-merge on selected GitHub changesets. When enabled, changesets will be automatically merged once all required status checks pass and any blocking reviews are resolved. This feature is GitHub-specific and requires [appropriate setup](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository) on the target repositories. Failed actions are listed under the bulk operations tab. |
4142

4243
## Monitoring bulk operations
4344

0 commit comments

Comments
 (0)