~sircmpwn/sr.ht-docs

88b52b86314f97d0c249edaffb0f0ab8490e0f0b — Andy Dulson 5 months ago bcb466d
Fix a typo in the build secrets tutorial: s/every/ever/
1 files changed, 1 insertions(+), 1 deletions(-)

M tutorials/builds.sr.ht/using-build-secrets.md
M tutorials/builds.sr.ht/using-build-secrets.md => tutorials/builds.sr.ht/using-build-secrets.md +1 -1
@@ 94,7 94,7 @@ when submitting build manifests from GitHub pull requests.

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,
particularly if using file secrets. If a secret is every leaked in this manner,
particularly if using file secrets. If a secret is ever leaked in this manner,
you should consider that secret compromised - revoke it and generate a new one.

---