a0f18644d7
A Gitea Actions job runs in a different macOS security session than an interactive SSH login - login.keychain-db's unlock state and search-list membership don't reliably carry over across that boundary, so the identity was invisible to the job even after successful unlock. Point the workflow's unlock step at a dedicated ci-signing.keychain-db instead, created independent of any login session.
80 lines
2.2 KiB
YAML
80 lines
2.2 KiB
YAML