From 10495e9101c0fc0cf6d1eabc28144691722195ee Mon Sep 17 00:00:00 2001 From: Maedah Batool Date: Tue, 27 May 2025 23:04:14 -0700 Subject: [PATCH 1/4] Batch Changes Docs Updates for 6.4 --- docs/batch-changes/how-src-executes-a-batch-spec.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/batch-changes/how-src-executes-a-batch-spec.mdx b/docs/batch-changes/how-src-executes-a-batch-spec.mdx index f3624095a..a3efb1cc8 100644 --- a/docs/batch-changes/how-src-executes-a-batch-spec.mdx +++ b/docs/batch-changes/how-src-executes-a-batch-spec.mdx @@ -23,6 +23,7 @@ Here, you will learn what happens when a user applies or previews a Batch Spec b - [Sending changeset specs](#sending-changeset-specs) - [Sending the batch spec](#sending-the-batch-spec) - [Preview or apply the batch spec](#preview-or-apply-the-batch-spec) + - [Halt execution](#halt-execution) The only difference is the last step, i.e., Preview or apply the batch spec. Here, the `src batch apply` command applies the batch spec, and the `src batch preview` prints a URL that gives you a preview of what would change if you applied the batch spec. @@ -185,3 +186,7 @@ That request yields an ID uniquely identifying this expanded batch spec version. If `src batch apply` was used, then the ID of the batch change is used to send another request to the Sourcegraph instance to apply the batch spec. If `src batch preview` was used to execute and create the batch spec, then a URL is printed, pointing to a preview page on the Sourcegraph instance, on which you can see what would happen if you were to apply the batch spec. + +### Halt execution + +If you encounter an error while running the `src batch preview` command, there is a fail-fast mode that halts the batch change execution immediately. To implement this, you can add a `-fail-fast` flag to the `src batch preview` and `src batch apply` commands. Once added, your execution should immediately halt on the first error instead of continuing with other repositories. This streamlines the iteration loop for users building a batch change who want to identify errors quickly. From 58d4152f474f8f0b00b1664bc87366a70558fbe5 Mon Sep 17 00:00:00 2001 From: Maedah Batool Date: Tue, 27 May 2025 23:14:26 -0700 Subject: [PATCH 2/4] Re-execute changesets --- docs/batch-changes/bulk-operations-on-changesets.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/batch-changes/bulk-operations-on-changesets.mdx b/docs/batch-changes/bulk-operations-on-changesets.mdx index 2351615c7..ec5a8a74d 100644 --- a/docs/batch-changes/bulk-operations-on-changesets.mdx +++ b/docs/batch-changes/bulk-operations-on-changesets.mdx @@ -37,6 +37,7 @@ Below is a list of supported bulk operations for changesets and the conditions w | **Close** | Close the selected changesets on the code hosts | | **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 | | **Export** | Export selected changesets that you can use for later use | +| **Re-execute** | Users can re-execute the changeset creation logic for selected workspaces. This allows for creating new changesets for users who are using non-deterministic run steps (for example,LLMs) | ## Monitoring bulk operations From 9532db9fd1b372aeed1e3fac10dbc6a942f4066b Mon Sep 17 00:00:00 2001 From: Maedah Batool Date: Tue, 27 May 2025 23:15:03 -0700 Subject: [PATCH 3/4] small imprv --- docs/batch-changes/bulk-operations-on-changesets.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/batch-changes/bulk-operations-on-changesets.mdx b/docs/batch-changes/bulk-operations-on-changesets.mdx index ec5a8a74d..a2b48cc43 100644 --- a/docs/batch-changes/bulk-operations-on-changesets.mdx +++ b/docs/batch-changes/bulk-operations-on-changesets.mdx @@ -37,7 +37,7 @@ Below is a list of supported bulk operations for changesets and the conditions w | **Close** | Close the selected changesets on the code hosts | | **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 | | **Export** | Export selected changesets that you can use for later use | -| **Re-execute** | Users can re-execute the changeset creation logic for selected workspaces. This allows for creating new changesets for users who are using non-deterministic run steps (for example,LLMs) | +| **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) | ## Monitoring bulk operations From 9a3281bd7bbc6629ad0cab128db84d2cf0eb784a Mon Sep 17 00:00:00 2001 From: Maedah Batool Date: Wed, 28 May 2025 11:53:09 -0700 Subject: [PATCH 4/4] BC updates --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 20ca1a558..667457315 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Sourcegraph Docs - + Welcome to the Sourcegraph documentation! We're excited to have you contribute to our docs. We've recently rearchitectured our docs tech stack — powered by Next.js, TailwindCSS and deployed on Vercel. This guide will walk you through the process of contributing to our documentation using the new tech stack.