We want to add either a step (or steps) or a separate pipeline that would run on our PRs but it shouldn't block merges. The reason for this is that we want to run a deploy-flow before merging but it should be possible to skip. We currently enforce one pipeline to pass for merging to be allowed so we don't want to includes this as normal steps in the pipeline we already have. What options do we have here? We saw forge could run custom merge checks but it doesn't seem trivial for a forge app to both checkout the code and actually run our scripts. I've also only seen that forge apps can add steps to an already existing pipeline, not execute an additional pipeline?
