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

So, for now I've gone with getting a list with GetRepositories from Github, and I check if the repository already exist. If it exists, add Import option instead of creating it. If anyone has a better solution, please share. :)

Do you mean having different environments on the same repo? You can achieve that using Github Actions and different branches. Look at this <https://www.pulumi.com/docs/guides/continuous-delivery/github-actions/>

It's not what I mean. I'm using NewRepository from the pulumi-github SDK on a project with several stacks, when I run `pulumi up` on dev stack it get's created, then i do `pulumi up` on prod stack it will become a conflict because repo already exists.

You could move github repository resources into a separate pulumi project/stack like `Pulumi.github.yaml` and use stack reference to get the resource values you need.