fix(CI): don't PR against "next" if we can't cleanly cherry pick #6703
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes what we saw happen in https://github.com/redwoodjs/redwood/actions/runs/3245650941. In this run, even though the fast-forward job couldn't cleanly cherry pick the commit in the squashed PR, the PR step could (somehow), and went ahead and made a PR. Let's just exit if the first step fails.
This PR also adds a
skip-cherry-pick
flag for PRs that will cleanly cherry pick but that we don't want in the next, like those in the last few commits.