# The Woodpecker secrets that EXIST in this repository's CI settings.
#
# One lowercase name per line; `#` starts a comment. This is not a
# configuration file — nothing reads it at build time. It is the list
# `scripts/check-ci-secrets.sh` holds `.woodpecker/**` against, so that a
# `from_secret:` naming a secret nobody created is refused on the push path
# instead of at 02:00 in a cron nobody reads.
#
# Why that is worth a file: in Woodpecker a `from_secret` whose secret does
# not exist is not a failure of the step that names it. It is a compile
# error for the ENTIRE pipeline — `status: error, workflows: 0` — so no step
# runs at all, including every step that had nothing to do with that secret.
# Cron run #434 (2026-09-19, on d7979113) ended exactly that way on
# `secret "site_ssh_target" not found`, and it took the forge publish, the
# gate and both builds down with it.
#
# ADDING A NAME HERE IS THE SECOND STEP, NEVER THE FIRST: create the secret
# in Repo -> Settings -> Secrets, see it in the list, and only then write it
# down here in the commit that starts using it. A name in this file that the
# server does not have is a lie this gate cannot detect — it can only check
# that somebody wrote the name down deliberately.
#
# Removing a secret from the server is the same move in reverse: stop using
# it, delete the line, push, and only then delete it in the UI.

codeberg_token
site_ssh_target
site_ssh_key
site_ssh_host_key
