Having a workflow that triggers multiple times for different apps within a monorepo

[kkortes]

Select Topic Area

Question

Body

I'm testing out nx right now and have two apps: apps/app-1 & apps/app-2. These apps are automatically deployed to Vercel on push via main-branch.

In the monorepo's root I have a single .github/e2e.yml file. It triggers on:

name: e2e
run-name: "${{ github.event.deployment_status.environment }}"
on: [deployment_status]

The setup allows me to trigger it after an app has been built and deployed on Vercel. In the same workflow I have access to a preview-url for that new deployment which I can run playwright- and/or cypress end-to-end test against.

The problem:
A workflow gets its own "github check" in a pull request.

My setup only creates one check named "e2e". The check's result will depend on the most recent deployment of any app. I would rather want one check per application deployed.

Is this achievable?

Sidenote: the standard, as far as I know, for when running monorepos is to trigger a "run all" via the workflow, which runs all tests in one go - which would provide the correct end result. Problem being I want a workflow to run every time something deploys individually, to have access to the preview-url for that deployment.

[kasparkallas]

Running into the exact same issue...

Vercel, monorepo, many deployments, single GitHub Action, and for some deployments we need to skip the tests which will override the status check result with unwanted "skip".

[yoieh]

Having the same issue here with a monorepo deploying on Vercel

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[CptJJ]

Same issue here, really a shame, wish there was more granularity to the deployment_status hook

[zhm]

Is there any solution or workaround to this? It seems like once a workflow is skipped it won't run it again even though it's a different app being deployed.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬