Take deployment environment into account when deciding what is affected

[MxKaras]

Our problem:

We have three environments in Github: dev, staging, and production. Our flow is that we deploy feature branches to dev, and when it is merged deploy to staging and then production. These latter two are both deploying main.

We are using this action with last-successful-event: deployment.

Right now npx nx affected -t deploy gives the following outcomes:

• dev: incremental deploy as expected ✅
• staging: incremental deploy as expected ✅
• production: nothing is deployed as there is already a successful deployment to main ❌

Proposed Solution:

Change the action to accept an optional deployment-environment that will be used when last-successful-event is deployment to differentiate between deployments to different environments.

[fvalmeida]

Hey, maintainers, do you have any recommendations on how to deal with this situation? There have been no comments so far, so I'm not sure if this is considered a problem to be addressed.