simply tagg conditions

.github/workflows/auto-update.yml

@@ -1,31 +1,9 @@
 name: auto-update
 on:
-  push: {}
-jobs:
-
-  validate-tag-if-present:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: TAGGED, Validate that the tag is in the correct format
-
-        run: |
-          echo "The GITHUB_REF: $GITHUB_REF"
-          #First check to see if the release is a tag
-          if [[ $GITHUB_REF =~ refs/tags/* ]]; then
-            #Yes, this is a tag, so we need to test to make sure that the tag
-            #is in the correct format (like v1.10.20)
-            if [[ $GITHUB_REF =~ refs/tags/v[0-9]+.[0-9]+.[0-9]+ ]]; then
-              echo "PASS: Tagged release with good format"
-              exit 0
-            else
-              echo "FAIL: Tagged release with bad format"
-              exit 1
-            fi
-          else
-          echo "PASS: Not a tagged release"
-          exit 0
-          fi                          
+  push:
+    branches:
+      - develop
+jobs:                       
   autoupdate:
     name: autoupdate
     runs-on: ubuntu-latest

detections/endpoint/7zip_commandline_to_smb_share_path.yml

@@ -5,7 +5,7 @@ date: '2021-08-17'
 author: Teoderick Contreras, Splunk
 status: production
 type: Hunting
-description: DAFTPUNK- This search is to detect a suspicious 7z process with commandline pointing
+description: This search is to detect a suspicious 7z process with commandline pointing
   to SMB network share. This technique was seen in CONTI LEAK tools where it use 7z
   to archive a sensitive files and place it in network share tmp folder. This search
   is a good hunting query that may give analyst a hint why specific user try to archive