fix(workflows): use correct name for patch

ZcashFoundation · Sep 25, 2023 · 59e8f11 · 59e8f11
1 parent 2cab03c
commit 59e8f11
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/.github/workflows/ci-unit-tests-docker.patch.yml b/.github/workflows/ci-unit-tests-docker.patch.yml
@@ -1,4 +1,4 @@
-name: CI Docker
+name: Docker Unit Tests
 
 # These jobs *don't* depend on cached Google Cloud state disks,
 # so they can be skipped when the modified files make the actual workflow run.

diff --git a/.github/workflows/ci-unites-tests-os.patch.yml b/.github/workflows/ci-unites-tests-os.patch.yml
@@ -1,4 +1,4 @@
-name: CI OSes
+name: Multi-OS Unit Tests
 
 on:
   pull_request:

diff --git a/.github/workflows/sub-build-lightwalletd.patch.yml b/.github/workflows/sub-build-lightwalletd.patch.yml
@@ -1,4 +1,4 @@
-name: zcash-lightwalletd
+name: Build lightwalletd
 
 # When the real job doesn't run because the files aren't changed,
 # run a fake CI job to satisfy the branch protection rules.

diff --git a/.github/workflows/sub-build-lightwalletd.yml b/.github/workflows/sub-build-lightwalletd.yml
@@ -1,6 +1,6 @@
 # TODO: we should stop using this build approach with lightwalletd and move to using our
 # reusable workflow to building all the docker images of our repo 
-name: zcash-lightwalletd
+name: Build lightwalletd
 
 # Ensures that only one workflow task will run at a time. Previous builds, if
 # already in process, will get cancelled. Only the latest commit will be allowed