Open ronaldtse opened 4 years ago
@dewyatt @ronaldtse Looks like we need to add secrets.PACKAGE_SIGNING_KEY_BASE64
and secrets.GITHUB_YUM_DEPLOY_KEY_BASE64
here. Also, there is github-release stage here, so I would need GITHUB_API_TOKEN too.
Do we still need to keep references to github.com/riboseinc/rpm-specs ?
@rrrooommmaaa You should have GitHub API token for the current repo out of the box. (Am I correct that this is the issue?) See: https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token.
@rrrooommmaaa sorry for missing this!
We do not need to reference https://github.com/riboseinc/rpm-specs .
@ribose-jeffreylau could you help setup these secrets (org-wide):
PACKAGE_SIGNING_KEY_BASE64
GITHUB_YUM_DEPLOY_KEY_BASE64
Thanks!
As title.