workflows/release-binaries: Restrict jobs based on owner instead of repo

[tstellar]

Not really any functional change, just a clean up that could make it easier to share snippets with other repos.

[llvmbot]

@llvm/pr-subscribers-github-workflow

Author: Tom Stellard (tstellar)

Changes

Not really any functional change, just a clean up that could make it easier to share snippets with other repos.

---

Full diff: https://github.com/llvm/llvm-project/pull/123797.diff

1 Files Affected:

• (modified) .github/workflows/release-binaries.yml (+3-3)

diff --git a/.github/workflows/release-binaries.yml b/.github/workflows/release-binaries.yml
index 29be8195da68ac..f9a264e7cf48f1 100644
--- a/.github/workflows/release-binaries.yml
+++ b/.github/workflows/release-binaries.yml
@@ -49,7 +49,7 @@ jobs:
   prepare:
     name: Prepare to build binaries
     runs-on: ${{ inputs.runs-on }}
-    if: github.repository == 'llvm/llvm-project'
+    if: github.repository_owner == 'llvm'
     outputs:
       release-version: ${{ steps.vars.outputs.release-version }}
       ref: ${{ steps.vars.outputs.ref }}
@@ -177,7 +177,7 @@ jobs:
   build-release-package:
     name: "Build Release Package"
     needs: prepare
-    if: github.repository == 'llvm/llvm-project'
+    if: github.repository_owner == 'llvm'
     runs-on: ${{ needs.prepare.outputs.build-runs-on }}
     steps:
 
@@ -327,7 +327,7 @@ jobs:
       - prepare
       - build-release-package
     if: >-
-      github.repository == 'llvm/llvm-project'
+      github.repository_owner == 'llvm'
     runs-on: ${{ needs.prepare.outputs.test-runs-on }}
     steps:
     - name: Checkout Actions

[boomanaiden154]

Is there an intention to use this or is this just general cleanup?

Anyways, LGTM.

[tstellar]

@boomanaiden154 It was a cleanup suggested here: #120786 (comment)

I also prefer this, because I think it looks better. Eventually I want to add a style guide for workflows that included things like this so we can be consistent.

[boomanaiden154]

I also prefer this, because I think it looks better. Eventually I want to add a style guide for workflows that included things like this so we can be consistent.

Makes sense to me. I've been meaning to write up something like that too, but haven't gotten around to it. Will happily review if you get to it before me.