runner/.forgejo/workflows/cascade-setup-forgejo.yml
Earl Warren 624b47bc2f
chore(ci): skip cascade if [skip cascade] is found in the PR title (#476)
When there are multiple PRs in flight, using a var to disable the cascading PR that eventually runs the end to end tests (for instance because the change is about examples) is error prone.

Allowing each pull request to indivudually decide when it is relevant or not is more practical and fine grain.

## Testing

Using [an extra commit](1b8949ed3a) for debuging:

- https://code.forgejo.org/forgejo/runner/actions/runs/3328 skips the cascade on this PR
- https://code.forgejo.org/forgejo/runner/actions/runs/3326 tries to run the cascade on this PR  (and fails because it does not have secrets) because `[skip ZZ cascade]` is set in the title

Reviewed-on: https://code.forgejo.org/forgejo/runner/pulls/476
Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>
2025-01-30 15:23:22 +00:00

28 lines
955 B
YAML

# SPDX-License-Identifier: MIT
on:
pull_request_target:
types:
- opened
- synchronize
- closed
jobs:
cascade:
runs-on: docker
container:
image: 'code.forgejo.org/oci/node:20-bookworm'
if: >
! contains(github.event.pull_request.title, '[skip cascade]')
steps:
- uses: https://code.forgejo.org/actions/cascading-pr@v2.2.0
with:
origin-url: ${{ env.GITHUB_SERVER_URL }}
origin-repo: forgejo/runner
origin-token: ${{ secrets.CASCADING_PR_ORIGIN }}
origin-pr: ${{ github.event.pull_request.number }}
destination-url: ${{ env.GITHUB_SERVER_URL }}
destination-repo: actions/setup-forgejo
destination-fork-repo: cascading-pr/setup-forgejo
destination-branch: main
destination-token: ${{ secrets.CASCADING_PR_DESTINATION }}
close-merge: true
update: .forgejo/cascading-pr-setup-forgejo