Create tutorial how to introduce and test changes for CI pipelines #82
Labels
area/ci
Relates to CI
area/community
Relates to all community activities
area/documentation
Relates to all activities around documentation
enhancement
New feature or request
Description
On our repos we use the
pull_request_target
event which takes the workflow definition from themain
branch. As a result, changes to anycapact/.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
The text was updated successfully, but these errors were encountered: