should I add my repo to <https://github.com/pulumi...
# pulumiverse
w
should I add my repo to https://github.com/pulumiverse/infra/tree/main/02-repositories so its CI is managed properly ?
l
Because this is an existing & migrated repo, we will take care of that because we need to import it in the Pulumi state.
w
👍
so should I want with setting up publish workflows as it’ll come from infra?
l
The workflows themselves won't come from infra, so please duplicate the release workflow from another repo. Keeping the workflow files up to date (like for the official providers in gh.com/pulumi), that's a totally different story.
w
oh I saw these https://github.com/pulumiverse/infra/tree/main/workflows/copied and thought they’re being reused I’m already reusing the ones here https://github.com/pulumiverse/infra/tree/main/.github/workflows would be nice to have a release one with optional inputs for language like the build workflow
if you could point me to a working release workflow I can convert it to a reusable one to be placed in infra
l
@white-chef-55657 don't bother on trying to get a reusable one in
infra
. I'm working with our engineering team to get https://github.com/pulumi/ci-mgmt working for 3rd party providers. I will create Github issues for things not working and might ask for some help on these. The mentioned repo is where the engineering team itself keeps the workflow files (and accompanying files) up to date for the whole set of providers they manage.
w
sounds good
can you approve https://github.com/pulumiverse/pulumi-vercel/pull/39 so I can give it a try? any chance I can get an admin on the repo or ability to bypass branch protection rules as a single maintainer ?
l
@white-chef-55657 did you use a working release workflow from a
pulumiverse
repo? In Pulumiverse, we don't have Java publishing yet, neither Slack alerting.
w
l
w