From ae32ebcc3c637902b8e62d549a02d537be76343c Mon Sep 17 00:00:00 2001 From: Jarek Potiuk <jarek@potiuk.com> Date: Fri, 10 Jan 2025 16:24:33 +0100 Subject: [PATCH] Remove contents: write permission from generate-constraints (#45558) The write permission cannot be set for PRs from forks in the call workflow - so we have to come back to implicit permissions and make explicit permissions passing a bit differently. --- .github/workflows/generate-constraints.yml | 6 ------ 1 file changed, 6 deletions(-) diff --git a/.github/workflows/generate-constraints.yml b/.github/workflows/generate-constraints.yml index 19592dae295c5..740310e1cc09b 100644 --- a/.github/workflows/generate-constraints.yml +++ b/.github/workflows/generate-constraints.yml @@ -44,12 +44,6 @@ on: # yamllint disable-line rule:truthy description: "Whether to use uvloop (true/false)" required: true type: string -permissions: - # This permission is only active for "canary" builds and PRs from the main repo - # All fork PRs are not allowed to have write permissions and this one is automatically downgraded to read - # Branch protection also prevents from pushing to the "code" branches so we can safely use this one to - # Push constraints to "constraints" branches which are non-code branches and are not protected - contents: write jobs: generate-constraints: permissions: