This message was deleted.

sparse-intern-71089

09/27/2023, 6:48 PM

This message was deleted.

limited-rainbow-51650

09/28/2023, 6:52 AM

@bulky-hamburger-30930 have you tried adding this to your workflow file at top level?

Copy code

permissions:
  pull-requests: write

https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs

bulky-hamburger-30930

10/02/2023, 4:03 PM

Just tried. It does not work. https://github.com/pulumiverse/pulumi-zitadel/pull/13/files#diff-59bb78345f0191afed346e77f9583230ea1ebfe2a59275e84bfac60b5914e0b6R10 Sorry for my example. It only consists of one command that is failing for upgrade-provider. Unfortunately I cannot do it with upgrade-provider because I already upgraded everything manually. But the next upgrade will fail for sure. Could you please enable the check for both repos?

bulky-hamburger-30930

10/02/2023, 4:25 PM

You can take a look at vercel repo settings. I guess it has this check activated. Otherwise, this CI would fail https://github.com/pulumiverse/pulumi-vercel/blob/main/.github/workflows/upgrade-provider.yml

bulky-hamburger-30930

10/04/2023, 3:23 PM

@limited-rainbow-51650 could you please help me?

bulky-hamburger-30930

10/09/2023, 11:50 AM

@limited-rainbow-51650 can you set this check for my repos?

6 Views

Open in Slack

Previous Next

Pulumi Community

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.