Merge branch 'main' into sg-next-apr-2025

Author: MaedahBatool

docs/admin/config/authorization_and_authentication.mdx

@@ -112,13 +112,7 @@ And configure the identity provider to pass the email address as the `nameID`.
 
 ### Bitbucket Server / Bitbucket Data Center authorization
 
-We do not currently support OAuth for Bitbucket Server or Bitbucket Data Center. You will need to combine permissions syncing from Bitbucket Server / Bitbucket Data Center with another authentication mechanism (SAML, built-in auth, HTTP authentication proxies). Bitbucket Server and Bitbucket Data Center only pass usernames to Sourcegraph, so you’ll need to make sure that those usernames are matched by whatever mechanism you choose to use for access.
-
-Follow the steps to [sync Bitbucket Server / Bitbucket Data Center permissions](/admin/code_hosts/bitbucket_server#repository-permissions). Then, do one of the following:
-
-1. Create the user accounts in Sourcegraph with matching usernames. (Access using `builtin` auth.)
-2. [Configure SAML authentication](/admin/auth/saml/). If you are using Bitbucket Server / Bitbucket Data Center, the `login` attribute is _not_ optional. You need to pass the Bitbucket Server username as the `login` attribute.
-3. [Configure an HTTP authentication proxy](/admin/auth/#http-authentication-proxies), passing the Bitbucket Server username value as the `usernameHeader`.
+We support authentication through OAuth for Bitbucket Server / Bitbucket Data Center. See the [Bitbucket Server auth provider docs](/admin/auth/#bitbucket-server).
 
 ### Azure DevOps Services
 

docs/batch-changes/faq.mdx

@@ -65,6 +65,17 @@ However, [steps](/batch-changes/batch-spec-yaml-reference#steps-run) can run any
 - [Jira tickets](https://github.com/sourcegraph/batch-change-examples/blob/main/ticketing-systems/jira-tickets/README)
 - [GitHub issues](https://github.com/sourcegraph/batch-change-examples/blob/main/ticketing-systems/github-issues/README)
 
+## Can I use GitHub/GitLab runners to automate my batch changes?
+To an extent, yes, you can use GitHub Actions or GitLab CI/CD runners to automate Sourcegraph batch changes to allow you to trigger batch changes automatically after events like library updates or on a schedule. 
+The implementation requirements are network access where your CI/CD runners must be able to reach your Sourcegraph instance and have authentication through a Sourcegraph access token for API access along with appropriate permissions to create batch changes.
+
+If you'd want to implement this automation:
+
+The best way would be to contact your SRE/Infrastructure team to verify if your CI/CD runners can access your Sourcegraph instance and if access is not available, work with your SRE team to request this capability.
+Once access is confirmed, you can proceed with implementing the automation
+
+However, this requires your CI/CD runners to have network access to your Sourcegraph instance. In many enterprise environments, this access may be restricted by default.
+
 ## What happens to the preview page if the batch spec is not applied?
 
 Unapplied batch specs are removed from the database after **seven days**.

public/llms.txt

@@ -105600,13 +105600,7 @@ And configure the identity provider to pass the email address as the `nameID`.
 
 ### Bitbucket Server / Bitbucket Data Center authorization
 
-We do not currently support OAuth for Bitbucket Server or Bitbucket Data Center. You will need to combine permissions syncing from Bitbucket Server / Bitbucket Data Center with another authentication mechanism (SAML, built-in auth, HTTP authentication proxies). Bitbucket Server and Bitbucket Data Center only pass usernames to Sourcegraph, so you’ll need to make sure that those usernames are matched by whatever mechanism you choose to use for access.
-
-Follow the steps to [sync Bitbucket Server / Bitbucket Data Center permissions](/admin/code_hosts/bitbucket_server#repository-permissions). Then, do one of the following:
-
-1. Create the user accounts in Sourcegraph with matching usernames. (Access using `builtin` auth.)
-2. [Configure SAML authentication](/admin/auth/saml/). If you are using Bitbucket Server / Bitbucket Data Center, the `login` attribute is _not_ optional. You need to pass the Bitbucket Server username as the `login` attribute.
-3. [Configure an HTTP authentication proxy](/admin/auth/#http-authentication-proxies), passing the Bitbucket Server username value as the `usernameHeader`.
+We support authentication through OAuth for Bitbucket Server / Bitbucket Data Center. See the [Bitbucket Server auth provider docs](/admin/auth/#bitbucket-server).
 
 ### Azure DevOps Services
 

src/data/redirects.ts

@@ -1,5 +1,9 @@
 const redirectsData = [
-
+  {
+    source: "/docs/admin/deploy_executors",
+    destination: "https://sourcegraph.com/docs/admin/executors/deploy_executors",
+    permanent: true
+  },
   {
     source: "/dev/roadmap",
     destination: "https://sourcegraph.com/direction",