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

You need to run the program with `pulumi up`, not as a regular node program.

The first line of imports should not be necessary.  You might want to start with a empty directory, run `pulumi new ts` and then copy/paste your code minus the first line.

<@U02R92PB7M5> if you want to run pulumi programs outside the `pulumi up` workflow, you'll need to use the automation API:

<https://github.com/pulumi/automation-api-examples/tree/main/nodejs/inlineProgram-ts>

This can be packaged as part of a yarn workflow

<@U02FZC2RE0Y> we do not want the Github-part to be a part of “pulumi up”. There is an automation API for this, but I cannot make it working with “@pulumi/github”. With “import { LocalProgramArgs, LocalWorkspace } from “@pulumi/pulumi/automation”;” or without, I still tge the same error.

<@UCWG26BH7> Yesm I saw this one, but it does not work in our environment:
awsume whatever
Session token will expire at 2021-12-24 02:28:41
[whatever] Role credentials will expire 2021-12-23 15:43:48
yarn install
yarn install v1.22.17
[1/4] :mag:  Resolving packages...
success Already up-to-date.
:sparkles:  Done in 0.10s.
yarn start
yarn run v1.22.17
$ tsc &amp;&amp; node ./bin/index.js
successfully initialized stack
installing plugins...
plugins installed
setting up config
config set
refreshing stack...
CommandError: code: 255
 stdout:
 stderr: error: getting secrets manager: passphrase must be set with PULUMI_CONFIG_PASSPHRASE or PULUMI_CONFIG_PASSPHRASE_FILE environment variables
But it goes into a wrong direction. I simply would like to use @pulumi/github” to create a repo. Without any involvement of our actual Pulumi stacks, if possible. Do you have any idea how to achieve this?

Do you want Pulumi to manage the lifecycle of the repository (create/update/delete), or are you just trying to automate the creation of repositories?  If it's the latter, you don't need Pulumi at all - just use Octokit.  <https://github.com/octokit/octokit.js>