Invalidating Signed Pipeline Yaml

[hikerspath]

Functionally, this extension alters yaml that is sent back to drone-server for scheduling. Because of this, we are encountering a runtime issue on any signed repository when paths is invoked.

Steps to reproduce

Steps to reproduce the behavior:

1. Create a pipeline that will trigger paths plugin
2. Sign the pipeline drone sign --save <repo>
3. Submit a pull-request
4. You will be asked to approve the pipeline

Expected behavior

Pipeline validation should happen regardless of the changes paths makes to the yaml file based on pre-configured matches (or lack of the same). Perhaps validation of the signed pipeline needs to happen within or prior to a pipeline run?

Screenshots

No screenshot here, but very reproducible, it will ask for permission inside the UI from an admin on the repository.

Environment (anything that would help us investigate the bug)

• OS Linux
• Version Drone 2.11.0 / Paths 1.0.0
• Browser Chrome, Safari