Closed yegorich closed 3 years ago
This is WiP. At least the whole testing process starts. But I don't know how to deal with pgp issues. It seems like we need at least to export GPG_TTY:
export GPG_TTY=$(tty)
Any ideas? I'm quite new to GitHub Actions.
I know that particular problem, and I recall documenting it the README.md. But I don't yet have any experience with GitHub Action so can't in that regard.
So, the first concept is working. I've created the following secrets for my fork:
FREIGHT_GPG_KEY_FIRST
FREIGHT_GPG_KEY_SECOND
FREIGHT_KEY_PASSWD
With these env variables I can import key and also create a passphrase file for apt. Now we need them for the main repository. The keys were exported as follows (as mentioned here):
gpg --export-secret-keys YOUR_ID_HERE | base64 > private.key
If I should add those secrets, I need admin privileges.
GitHub repository needs two secrets and a passphrase that will be imported before the make check can be invoked:
To avoid interactive password request from apt a passphrase file will be used.