On our repos we use the pull_request_target event which takes the workflow definition from the main branch. As a result, changes to any capact/.github/workflows/*.yaml files on pull-request are ignored on PRs. This makes our CI more secure. But at the same time, it's problematic to test that change. The only way is to test it on your fork.
Reason
External contributors don't know how to test changes proposed to our CI. It's also problematic for core-devs to describe the testing path each time.
Use cases
Capact Developer:
reduce time spend on explaining how to test changes on CI.
gives a reproducible scenario that all can follow for testing changes on CI.
Description
On our repos we use the
pull_request_targetevent which takes the workflow definition from themainbranch. As a result, changes to anycapact/.github/workflows/*.yamlfiles on pull-request are ignored on PRs. This makes our CI more secure. But at the same time, it's problematic to test that change. The only way is to test it on your fork.Reason
External contributors don't know how to test changes proposed to our CI. It's also problematic for core-devs to describe the testing path each time.
Use cases