Add thread_id to on-hold job

.circleci/test-deploy.yml

@@ -22,6 +22,12 @@ jobs:
     executor: <<parameters.runner>>
     steps:
       - checkout
+      - slack/notify:
+          debug: true
+          step_name: "Initial message with thread"
+          template: basic_success_1
+          event: always
+          thread_id: orb-testing-thread-<${CIRCLE_SHA1}>
       - slack/notify:
           debug: true
           step_name: "Custom template with group mention"
@@ -232,6 +238,12 @@ workflows:
           matrix:
             parameters:
               runner: [cimg, mac, alpine, windows]
+      - slack/on-hold:
+          context: SLACK_NOTIFICATIONS_TEST
+          debug: true
+          step_name: "On hold with thread"
+          template: basic_success_1
+          thread_id: orb-testing-thread-<${CIRCLE_SHA1}>
       - orb-tools/pack:
           filters: *release-filters
       - orb-tools/publish:

src/jobs/on-hold.yml

@@ -55,6 +55,14 @@ parameters:
     type: string
     default: Slack - Sending Notification
     description: Specify a custom step name for this command, if desired
+  thread_id:
+    type: string
+    default: ""
+    description: |
+      When set, the first `notify` with a given `thread_id` will appear as a regular slack message.
+      Any subsequent `notify` usage with the same identifier will be posted within the initial message's thread.
+      `thread_id` should be set to any arbitrary string to help you identify different threads. See examples for more information.
+      Enabling thread messages with this parameter implies using a very small amount of cacheing: ~200 B
 
 docker:
   - image: cimg/base:stable
@@ -72,3 +80,4 @@ steps:
       debug: <<parameters.debug>>
       circleci_host: <<parameters.circleci_host>>
       step_name: <<parameters.step_name>>
+      thread_id: <<parameters.thread_id>>