"github actions" question: If the files in the path to the pulumi program/project didn't change, we'd like to not run the pulumi step in our workflow job which handles applying those changes. (We know pulumi does the right thing, but this relates to dev process stuff - it's specifically about our cloud "development" environment, not any of our higher environments.) We've got that working. But our deployment job in the same workflow needs the output of the pulumi program so that it has the app service name to which to deploy (since the app service name has the pulumi-generated suffix). If we just skip the pulumi step in that job, then the output isn't available; and the github action fails. It looks like our best option might be to use the "expect-no-changes" option to the pulumi github action. I don't see any examples of specifically how to use that option - I'm guessing it's just another line in the yaml under "with:". Any thoughts on this?

Your 2nd step shouldn't use the "console output" of the 1st step. Instead, it should get the outputs using Pulumi.

pulumi stack output

can do this.

I'm not using console output. I'm using what pulumi emits via an [Output] attribute. That's following an example in the docs for the pulumi github action. It's been working for a year, so I'm not concerned about that. The situation I realized I'd put myself in is that if the pulumi step does not run at all (based on the conditional I had added) then there is no output for my deployment step to use. Thanks for the reply.