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

has anyone used the github provider `pull_request` resource?

<https://www.pulumi.com/registry/packages/github/api-docs/repositorypullrequest/>

<https://registry.terraform.io/providers/integrations/github/latest/docs/resources/repository_pull_request>

This one seems a bit weird. Like you’d have to constantly be adding resources to a stack (new pull requests), or you need to automatically “forget” the resource, so you can recreate it? (`pulumi state rm`)

I’m curious if anyone has used this before, and how they are using it.

From the upstream documentation:

&gt; // It’s not entirely clear how to treat PR deletion according to Terraform’s
&gt; // CRUD semantics. The approach we’re taking here is to close the PR unless
&gt; // it’s already closed or merged. Merging it feels intuitively wrong in what
&gt; // effectively is a destructor.
<https://github.com/integrations/terraform-provider-github/blob/main/github/resource_github_repository_pull_request.go#L256>

I guess this makes sense.