From a0a3d8f1e7862e58e74574cde171ef58e5ed5179 Mon Sep 17 00:00:00 2001 From: zachel Date: Thu, 26 Jan 2023 15:03:45 +0900 Subject: 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) --- builds.sr.ht/index.md | 16 +--------------- 1 file changed, 1 insertion(+), 15 deletions(-) (limited to 'builds.sr.ht') 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 -- cgit