aboutsummaryrefslogtreecommitdiffstats
path: root/tutorials/builds.sr.ht/using-build-secrets.md
diff options
context:
space:
mode:
Diffstat (limited to 'tutorials/builds.sr.ht/using-build-secrets.md')
-rw-r--r--tutorials/builds.sr.ht/using-build-secrets.md3
1 files changed, 1 insertions, 2 deletions
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,