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

<@UKHFQ233Q> <@UMP2PT80L> <@U04LG89SXS8> bumping this issue again hoping this could get priority: <https://github.com/pulumiverse/infra/issues/298>

<@UK4HNFLCB> I did a quick research at GitHub and their documentation about those "bot accounts" is ... let's simply call it confusing. What type of "bot account" is needed here? As far as I understood the "bot account" shall be used to run the scripts (worklow) from `ci-mgmt` to create PRs that will (auto-)update the build infrastructure and even the (bridged) provider itself. Main issue from my side is right now, aside I don't know what "bot user" we need here, how do we do this in a secure manner, i.e. we need a controlled way to "onboard" Pulumiverse provider repos onto the "bot account" and to `ci-mgmt`

Oh and the documentation in `ci-mgmt` is written for Pulumi itself, because I don't see any possibility to specify that the provider is hosted in the `pulumiverse` org and NOT in the `pulumi` org.

<@UKHFQ233Q> maybe put this conversation on the issue.