Remove all references to dispatch.sr.ht

This patch removes remaining references to dispatch.sr.ht
that were left inside the docs after dispatch.sr.ht was
removed (commit aea6609d9595)

11 files changed, 8 insertions, 60 deletions

diff --git a/builds.sr.ht/index.md b/builds.sr.ht/index.md
index b127d39..66c1297 100644
--- a/builds.sr.ht/index.md
+++ b/builds.sr.ht/index.md
@@ -118,8 +118,7 @@ but any code run as a side-effect, like your Makefile.
 
 This is done for you automatically whenever you submit builds using sr.ht
 features. When building patches from your mailing list, sr.ht will automatically
-disable secrets. The same is true of pull requests from GitHub submitted via
-dispatch.sr.ht.
+disable secrets.
 
 In any case, if your secret is leaked, you **must** consider it permanently
 compromised, revoke it from any services it provides authentication for, and
@@ -179,19 +178,6 @@ results page](https://builds.sr.ht/~sircmpwn?search=scheduled+image+refresh) or
 Do you have something that integrates with builds.sr.ht? Submit a patch for this
 page!
 
-## dispatch.sr.ht
-
-[dispatch.sr.ht](https://dispatch.sr.ht) offers a variety of integrations with
-builds.sr.ht, including support for connecting builds.sr.ht to external services
-like GitHub. This should be your first stop when looking for an integration.
-
-**Environment**
-
-- `BUILD_SUBMITTER`: `dispatch.sr.ht`
-- `BUILD_REASON`: `github-commit` (commit from GitHub), `gitlab-commit`
-(commit from Gitlab), `github-pr` (pull request from GitHub) or
-`gitlab-mr` (merge request from Gitlab)
-
 ## git.sr.ht
 
 git.sr.ht will automatically submit builds for you if you store a manifest in
diff --git a/configuration.md b/configuration.md
index c6e680e..c0f92a2 100644
--- a/configuration.md
+++ b/configuration.md
@@ -11,7 +11,6 @@ certain aspects which are described below. Be sure to take a look at each
 service's configuration page for more details:
 
 - [builds.sr.ht](/builds.sr.ht/configuration.md)
-- [dispatch.sr.ht](/dispatch.sr.ht/configuration.md)
 - [git.sr.ht](/git.sr.ht/configuration.md)
 - [hg.sr.ht](/hg.sr.ht/configuration.md)
 - [lists.sr.ht](/lists.sr.ht/configuration.md)
diff --git a/installation.md b/installation.md
index 82afa56..895de85 100644
--- a/installation.md
+++ b/installation.md
@@ -28,7 +28,6 @@ have their own, unique requirements that necessitate extra installation steps.
 As such, be sure to consult each service's installation page for more details:
 
 - [builds.sr.ht](/builds.sr.ht/installation.md)
-- [dispatch.sr.ht](/dispatch.sr.ht/installation.md)
 - [git.sr.ht](/git.sr.ht/installation.md)
 - [hg.sr.ht](/hg.sr.ht/installation.md)
 - [hub.sr.ht](/hub.sr.ht/installation.md)
diff --git a/meta.sr.ht/oauth-api.md b/meta.sr.ht/oauth-api.md
index a4e43c5..1c826a2 100644
--- a/meta.sr.ht/oauth-api.md
+++ b/meta.sr.ht/oauth-api.md
@@ -98,7 +98,6 @@ recognized:
 - `todo.sr.ht`
 - `lists.sr.ht`
 - `man.sr.ht`
-- `dispatch.sr.ht`
 
 ### The application redirect
 
diff --git a/ops/builds.sr.ht-migration.md b/ops/builds.sr.ht-migration.md
index fc06748..73df3db 100644
--- a/ops/builds.sr.ht-migration.md
+++ b/ops/builds.sr.ht-migration.md
@@ -65,11 +65,11 @@ single account and let us know. If you set up a dedicated organization account,
 and one or more of your members has a paid sr.ht account, let us know and we'll
 link the billing so that you don't have to pay twice.
 
-## What about builds submitted for patches or pull requests?
+## What about builds submitted for patches?
 
-Jobs submitted to run tests against patches sent to mailing lists, or for GitHub
-or GitLab events via dispatch.sr.ht, are submitted under the project owner's
-account. This account is the one that needs to be paid — not the accounts
+Jobs submitted to run tests against patches sent to mailing lists
+are submitted under the project owner's account.
+This account is the one that needs to be paid — not the accounts
 of those submitting patches or pull requests.
 
 # Community discussion
diff --git a/ops/robust-psql.md b/ops/robust-psql.md
index cb84814..e8890bb 100644
--- a/ops/robust-psql.md
+++ b/ops/robust-psql.md
@@ -150,7 +150,6 @@ hosts=meta.sr.ht \
   lists.sr.ht \
   todo.sr.ht \
   man.sr.ht \
-  dispatch.sr.ht \
   paste.sr.ht \
   hub.sr.ht \
   cirno1.sr.ht \
diff --git a/ops/topology.md b/ops/topology.md
index 005d885..3c8d964 100644
--- a/ops/topology.md
+++ b/ops/topology.md
@@ -88,7 +88,6 @@ Host IP: 208.88.54.61 (**old subnet**), 2604:bf00:710:0:230:48ff:fedc:ab06
 
 - drewdevault.com-b: 173.195.146.137
 - todo.sr.ht: 173.195.146.145, 2604:bf00:710:0:5054:ff:fea1:a941
-- dispatch.sr.ht: 173.195.146.147, 2604:bf00:710:0:5054:ff:fe44:efcb
 - pages.sr.ht: 173.195.146.139
 - feeds.drewdevault.com: 173.195.146.132
 
diff --git a/support.md b/support.md
index b8ec817..a6b52da 100644
--- a/support.md
+++ b/support.md
@@ -60,7 +60,6 @@ Each service of sr.ht has a dedicated bug tracker:
 - [man.sr.ht](https://todo.sr.ht/~sircmpwn/man.sr.ht)
 - [meta.sr.ht](https://todo.sr.ht/~sircmpwn/meta.sr.ht)
 - [paste.sr.ht](https://todo.sr.ht/~sircmpwn/paste.sr.ht)
-- [dispatch.sr.ht](https://todo.sr.ht/~sircmpwn/dispatch.sr.ht)
 - [pages.sr.ht](https://todo.sr.ht/~sircmpwn/pages.sr.ht)
 
 There is also a [general-purpose bug
diff --git a/tutorials/builds.sr.ht/github-integration.md b/tutorials/builds.sr.ht/github-integration.md
index a26806f..c5f4056 100644
--- a/tutorials/builds.sr.ht/github-integration.md
+++ b/tutorials/builds.sr.ht/github-integration.md
@@ -100,38 +100,9 @@ different names for packages, different distributions of coreutils, and so on.
 
 ## Adding these builds to your GitHub repository
 
-Try making a new "mrsh" repository on your GitHub account. Note that forks won't
-work — so make sure you make a *new* repository and push the mrsh code to it.
-Take a look at the `.builds` directory in mrsh: each of these build manifests
-can be submitted on push or pull request by rigging up a dispatch.sr.ht task.
+Since 2022-10-01, dispatch.sr.ht is now deprecated.
 
-Go to [dispatch.sr.ht](https://dispatch.sr.ht) and "Configure new task". Pick
-"GitHub commits > builds.sr.ht jobs" and click "Add task" for your new mrsh
-repository. That's all you have to do! Now let's make a dummy commit and push it
-to GitHub to test it out:
-
-    git commit --allow-empty -m "Testing builds.sr.ht"
-    git push
-
-Head over to your [builds.sr.ht dashboard](https://builds.sr.ht) and you should
-see your build begin momentarily!
-
-## Testing pull requests on GitHub
-
-If you want to run your CI against pull requests on GitHub, follow a similar
-procedure, but select "GitHub pull requests > builds.sr.ht jobs" instead. Then,
-each new pull request that comes into your repo will be built on builds.sr.ht
-and the pull request status updated with the build results.
-
-## Why doesn't my GitHub repo show up?
-
-There are a couple of limitations:
-
-- Forks are not supported
-- You must have admin access to the repo (test this by trying to add a webhook
-  through the GitHub UI manually)
-
-If neither of these are the issue, [write us an email](mailto:sir@cmpwn.com).
+See [hottub](https://sr.ht/~emersion/hottub) for third-party integration.
 
 ---
 
@@ -144,4 +115,3 @@ Other resources:
 
 - [builds.sr.ht user manual](/builds.sr.ht)
 - [Build manifest reference](/builds.sr.ht/manifest.md)
-- [dispatch.sr.ht](/dispatch.sr.ht)
diff --git a/tutorials/builds.sr.ht/using-build-secrets.md b/tutorials/builds.sr.ht/using-build-secrets.md
index 47e74e8..1907be6 100644
--- a/tutorials/builds.sr.ht/using-build-secrets.md
+++ b/tutorials/builds.sr.ht/using-build-secrets.md
@@ -89,8 +89,7 @@ The easiest way to control whether or not secrets work in your build is by
 turning them off via the API: if you set secrets=false in [POST
 /api/jobs](/builds.sr.ht/api.md#post-apijobs), the secrets will not be resolved.
 This is automatically done in many places where the build manifest could be
-modified by an untrusted party — for example, dispatch.sr.ht disables secrets
-when submitting build manifests from GitHub pull requests.
+modified by an untrusted party.
 
 However, some degree of responsibility lies with you for keeping your secrets
 secure. Avoid writing build manifests that would print your secrets to the logs,
diff --git a/tutorials/getting-started-with-builds.md b/tutorials/getting-started-with-builds.md
index ab534ef..bcbc0a0 100644
--- a/tutorials/getting-started-with-builds.md
+++ b/tutorials/getting-started-with-builds.md
@@ -140,4 +140,3 @@ Other resources:
 
 - [builds.sr.ht user manual](/builds.sr.ht)
 - [Build manifest reference](/builds.sr.ht/manifest.md)
-- [dispatch.sr.ht](/dispatch.sr.ht)