From 00db2dee5607cf959b2c6b9ee36dbe8ce3cd12eb Mon Sep 17 00:00:00 2001 From: Marc LeBlanc <7050295+marcleblanc2@users.noreply.github.com> Date: Tue, 15 Sep 2026 15:02:06 -0600 Subject: [PATCH] test: Example PR that fails the link check (do not merge) Adds an absolute link to a moved page on this site, a link to a heading that does not exist, and a dead external link. Amp-Thread-ID: https://ampcode.com/threads/T-01a0a6dc-7fb8-766d-8e8d-c2fda22ee1ce Co-authored-by: Amp --- docs/batch-changes/server-side.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/batch-changes/server-side.mdx b/docs/batch-changes/server-side.mdx index c301fa1d8..0b4ea2502 100644 --- a/docs/batch-changes/server-side.mdx +++ b/docs/batch-changes/server-side.mdx @@ -37,6 +37,8 @@ Running batch changes server-side has been tested to run a simple **45K changese By default, docker on mac will build docker images for `linux/arm64`, which will result in errors when running server-side because executors provide `linux/amd64` hosts. If you're creating your own images to run in batch changes, this can be a problem. Use the `--platform linux/amd64` flag with `docker build` to build images compatible with the server-side host. +See [deploying executors](https://sourcegraph.com/docs/admin/executors/deploy_executors), the [Docker image settings](/batch-changes/server-side#docker-image-settings), and the [executor image list](https://github.com/sourcegraph/sourcegraph/blob/main/executor-images.md) for details. + ## Using file mounts with server-side execution