Skip to content

Create tutorial how to introduce and test changes for CI pipelines #82

@mszostok

Description

@mszostok

Description

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/ciRelates to CIarea/communityRelates to all community activitiesarea/documentationRelates to all activities around documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions