Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much. - Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/) Signed-off-by: naveen <172697+naveensrinivasan@users.noreply.github.com>
18 lines
306 B
YAML
18 lines
306 B
YAML
name: Smoke tests on DUTs
|
|
|
|
on:
|
|
workflow_dispatch:
|
|
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
|
|
Smoke:
|
|
permissions:
|
|
contents: none
|
|
if: ${{ github.repository_owner == 'Armbian' }}
|
|
uses: armbian/scripts/.github/workflows/smoke-tests.yml@master
|
|
secrets:
|
|
KEY_CI: ${{ secrets.KEY_CI }}
|