Matching behaviour between Vercel's ignored build step and GitHub Actions

[mrmckeb]

Summary

Hi team, I was wondering what the current "best practice" is for syncing behaviours for ignoring builds, now that there are new Turborepo features like --affected.

I saw that --affected also has built-in logic for GitHub actions which is great:
https://turbo.build/repo/docs/crafting-your-repository/constructing-ci#using---affected-in-github-actions

---

The docs here explain how to run end-to-end tests on a deployment status:
https://vercel.com/guides/how-can-i-run-end-to-end-tests-after-my-vercel-preview-deployment

We've recently turned on Vercel's ignored build step feature, using npx turbo-ignore --fallback=HEAD^, which means we can no longer require that job without additional configuration. We are happy to make a change to that command there's a better option.

What's the recommended approach to mirror behaviour between Vercel's ignored build step and a GitHub actions step, so that I can know if I will or won't receive a deployment_status event for a given commit?

I realise that I'll also need to check the history of that branch, because a previous commit may have had a deployment - even if the latest commit does not - which means the tests for that branch should still be marked as failing or passing.

Additional information

No response

Example

No response