No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Does anyone have recommendations on how to think about the boundaries between Pulumi Deployments (enabled via UI + GitHub integration) and general Pulumi CI/CD? It seems like deployments enables running `pulumi up` on every commit that happens on a branch, say, the `main` branch. This would mean that only after you merge a PR does `pulumi` run. What do people do to preview changes during the branch development?

When you open a PR against the main branch a PR should run and comment on the PR automatically.

Will it just run `preview` on the PR and then once it merges it runs `up`?

And for local development during the branch, do you recommend working on temporary stacks?  <https://www.pulumi.com/blog/iac-recommended-practices-developer-stacks-git-branches/>

&gt; And for local development during the branch
There are a couple of options here:

1. you can create a new branch and a new stack, and then set deployment settings on that branch, including OIDC, etc. That way a developer can just push commits to a branch and the stack automatically gets updated in the background. 
2. you can create a new branch and stack, and then have the developer run `pulumi up` locally, but this requires giving them cloud credentials on their local machine
Both are great workflows.