3 Commits

Author	SHA1	Message	Date
StepSecurity Bot	56d08e1b4d	ci: Harden GitHub Actions ... Update GitHub actions to use full length commit ids for third-party actions to reduce security risk in case of vulnerabilities. Signed-off-by: StepSecurity Bot <bot@stepsecurity.io> Co-authored-by: Nikhil-Ladha <nikhilladha1999@gmail.com>	2024-09-19 11:00:39 +00:00
Niels de Vos	0e79135419	ci: prevent Retest Workflow from running on forked repos ... Forked repositories contain the the `.github/workflows/` directory, and therefore run all the GitHub Workflows located there. Some of the workflows need additional configuration, like providing access to the standard `GITHUB_TOKEN`. If the extra configuration is not done, the GitHub Workflow will fail, and the owner of the forked repository will receive regular notifications about that. There is no need to run the "retest" workflow on forked repositories, so it can be skipped by default. Signed-off-by: Niels de Vos <ndevos@ibm.com>	2023-06-05 08:56:40 +00:00
naveen	2672fad90a	ci: Set permissions for GitHub actions ... 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-jobs/assigning-permissions-to-jobs Signed-off-by: naveen <172697+naveensrinivasan@users.noreply.github.com> naveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>	2022-05-05 20:21:15 +05:30