ceph-csi/.github/workflows/retest.yaml

---
name: "Retest approved pull Requests"
# yamllint disable-line rule:truthy
on:
  schedule:
    # Run the retest action every 30 minutes
    - cron: "30 * * * *"

permissions:
  contents: read

jobs:
  retest:
    if: github.repository == 'ceph/ceph-csi'
    runs-on: ubuntu-latest
    steps:
      # path to the retest action
      - uses: ceph/ceph-csi/actions/retest@devel
        with:
          GITHUB_TOKEN: ${{ secrets.CEPH_CSI_BOT_TOKEN }}
          required-label: "ci/retry/e2e"
          max-retry: "5"
          required-approve-count: "2"
ci: add action to retest failed approved PR's Adding github action to retest the failed approved PR's. sample output is available at https://github.com/Madhu-1/retest-action/pull/3 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> 2021-11-12 10:28:13 +00:00			`---`
			`name: "Retest approved pull Requests"`
			`# yamllint disable-line rule:truthy`
			`on:`
			`schedule:`
			`# Run the retest action every 30 minutes`
			`- cron: "30 * * * *"`
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-01 01:00:30 +00:00
			`permissions:`
			`contents: read`

ci: add action to retest failed approved PR's Adding github action to retest the failed approved PR's. sample output is available at https://github.com/Madhu-1/retest-action/pull/3 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> 2021-11-12 10:28:13 +00:00			`jobs:`
			`retest:`
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 07:30:41 +00:00			`if: github.repository == 'ceph/ceph-csi'`
ci: add action to retest failed approved PR's Adding github action to retest the failed approved PR's. sample output is available at https://github.com/Madhu-1/retest-action/pull/3 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> 2021-11-12 10:28:13 +00:00			`runs-on: ubuntu-latest`
			`steps:`
			`# path to the retest action`
			`- uses: ceph/ceph-csi/actions/retest@devel`
			`with:`
ci: use CEPH_CSI_BOT token for retest action For retest action's comment `@Mergifyio refresh` to be accepted by mergifyio, the bot should have write permissions to the repo. Therefore, use Ceph-csi-bot instead of github actions bot. Signed-off-by: Rakshith R <rar@redhat.com> 2022-03-18 04:48:21 +00:00			`GITHUB_TOKEN: ${{ secrets.CEPH_CSI_BOT_TOKEN }}`
ci: add action to retest failed approved PR's Adding github action to retest the failed approved PR's. sample output is available at https://github.com/Madhu-1/retest-action/pull/3 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> 2021-11-12 10:28:13 +00:00			`required-label: "ci/retry/e2e"`
			`max-retry: "5"`
			`required-approve-count: "2"`