From b8196accc369365ddbbfa062bd66bfa5e9769b2a Mon Sep 17 00:00:00 2001
From: "C.Lee Taylor" <47312074+leet4tari@users.noreply.github.com>
Date: Mon, 7 Aug 2023 09:54:11 +0200
Subject: [PATCH] ci(fix): artifact cleanup for diag-utils (#5613)

Description
Remove the diag-utils folder before syncing to storage

Motivation and Context
Improve the tari web site download listing.

How Has This Been Tested?
Builds in local fork

What process can a PR reviewer use to test or verify this change?
Check files been deleted in new step before s3 upload

<!-- Checklist -->
<!-- 1. Is the title of your PR in the form that would make nice release
notes? The title, excluding the conventional commit
tag, will be included exactly as is in the CHANGELOG, so please think
about it carefully. -->


Breaking Changes
---

- [x] None
- [ ] Requires data directory on base node to be deleted
- [ ] Requires hard fork
- [ ] Other - Please specify

<!-- Does this include a breaking change? If so, include this line as a
footer -->
<!-- BREAKING CHANGE: Description what the user should do, e.g. delete a
database, resync the chain -->
---
 .github/workflows/base_node_binaries.yml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/.github/workflows/base_node_binaries.yml b/.github/workflows/base_node_binaries.yml
index 0cc086e0ff..d8f481da96 100644
--- a/.github/workflows/base_node_binaries.yml
+++ b/.github/workflows/base_node_binaries.yml
@@ -439,6 +439,12 @@ jobs:
           name: ${{ env.TBN_FILENAME }}_archive-diag-utils-${{ matrix.builds.name }}
           path: "${{ github.workspace }}${{ env.TBN_DIST }}/diag-utils/*.zip*"
 
+      - name: Artifact cleanup for diag-utils
+        continue-on-error: true
+        shell: bash
+        run: |
+          rm -vRf "${{ github.workspace }}${{ env.TBN_DIST }}/diag-utils/"
+  
       - name: Sync dist to S3 - Bash
         continue-on-error: true # Don't break if s3 upload fails
         if: ${{ env.AWS_SECRET_ACCESS_KEY != '' && matrix.builds.runs-on != 'self-hosted' }}