Try to make the job name a little friendlier.

NVIDIA · Apr 22, 2024 · 0c8e770 · 0c8e770
1 parent 4a59779
commit 0c8e770
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 0 deletions.
diff --git a/.github/workflows/ci-dispatch-group.yml b/.github/workflows/ci-dispatch-group.yml
@@ -15,6 +15,7 @@ permissions:
 
 jobs:
   standlone-jobs:
+    name: '[Standalone]'
     permissions:
       id-token: write
       contents: read
@@ -30,6 +31,7 @@ jobs:
       command:  ${{ matrix.command }}
 
   two-stage-jobs:
+    name: '[TwoStage]'
     permissions:
       id-token: write
       contents: read

diff --git a/.github/workflows/ci-dispatch-two-stage.yml b/.github/workflows/ci-dispatch-two-stage.yml
@@ -15,6 +15,7 @@ permissions:
 
 jobs:
   producers:
+    name: '[Producer]'
     # It is impossible to accumulate output variables across a matrix, and we cannot rely on the results of the dispatch-job workflow to determine success.
     # See the note in ci-dispatch-job.yml for more information.
     #
@@ -34,6 +35,7 @@ jobs:
       command:  ${{ matrix.command }}
 
   consumers:
+    name: '[Consumer]'
     needs: producers
     # dispatch-job's result is always false, check the outputs instead. See ci-dispatch-job.yml for more information.
     if: ${{ !cancelled() && fromJson(needs.producers.outputs.success) }}