feat(ci-test-notify): add info status for informational notices

.github/actions/ci-test-notify/README.md

@@ -8,12 +8,12 @@ Replaces the nightly-specific `ci-notify-nightly-tests` action with a generic in
 
 <!-- AUTO-DOC-INPUT:START - Do not remove or modify this section -->
 
-|    INPUT    |  TYPE  | REQUIRED | DEFAULT |                                                                                         DESCRIPTION                                                                                         |
-|-------------|--------|----------|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-|   details   | string |  false   |         |                                               Markdown text appended after the build <br>URL (test results, versions, artifact links, etc.)                                                 |
-|   status    | string |   true   |         |         Run status, typically `needs.<job>.result` or `job.status`. <br>`success` and `failure` notify; `cancelled` and <br>`skipped` are treated as no-ops and <br>send nothing.           |
-|  test-name  | string |   true   |         | Test suite name for the header <br>(e.g. "E2E Ginkgo Nightly Tests"). Keep under ~130 chars — <br>Slack header blocks have a 150-char <br>limit and the status suffix takes <br>~15 chars.  |
-| webhook-url | string |   true   |         |                                                                                 Slack incoming webhook URL                                                                                  |
+|    INPUT    |  TYPE  | REQUIRED | DEFAULT |                                                                                                                                            DESCRIPTION                                                                                                                                             |
+|-------------|--------|----------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+|   details   | string |  false   |         |                                                                                                   Markdown text appended after the build <br>URL (test results, versions, artifact links, etc.)                                                                                                    |
+|   status    | string |   true   |         | Run status, typically `needs.<job>.result` or `job.status`. <br>`success` and `failure` notify; `cancelled` and <br>`skipped` are treated as no-ops and <br>send nothing. Use `info` for a <br>standalone informational notice (e.g. a deploy) that always <br>notifies with no pass/fail suffix.  |
+|  test-name  | string |   true   |         |                                                    Test suite name for the header <br>(e.g. "E2E Ginkgo Nightly Tests"). Keep under ~130 chars — <br>Slack header blocks have a 150-char <br>limit and the status suffix takes <br>~15 chars.                                                      |
+| webhook-url | string |   true   |         |                                                                                                                                     Slack incoming webhook URL                                                                                                                                     |
 
 <!-- AUTO-DOC-INPUT:END -->
 
@@ -29,6 +29,9 @@ Build URL: <link to workflow run>
 <repo> · Run #<number>
 ```
 
+`status: info` renders a 🚀 header with no `[status]` suffix, for informational
+notices (e.g. a deploy) rather than pass/fail results.
+
 ## Usage
 
 ### Nightly E2E tests
@@ -58,6 +61,24 @@ Build URL: <link to workflow run>
     webhook-url: ${{ secrets.SLACK_WEBHOOK_URL_CI_TESTS_ALERTS }}
 ```
 
+### Informational deploy notice
+
+`info` always notifies (no pass/fail suffix) and uses a 🚀 header, for a
+standalone notice such as a release candidate landing in staging:
+
+```yaml
+- uses: loft-sh/github-actions/.github/actions/ci-test-notify@ci-test-notify/v1
+  with:
+    test-name: Release candidate deployed to staging.vcluster.cloud
+    status: info
+    details: |
+      • vcluster-platform: `4.10.0-rc.1`
+
+      QA: spin up an instance on staging, verify it's healthy, then tick the
+      pre-release checklist.
+    webhook-url: ${{ secrets.SLACK_WEBHOOK_URL_QA }}
+```
+
 ### Failure-only with summary
 
 ```yaml

.github/actions/ci-test-notify/action.yml

@@ -8,7 +8,7 @@ inputs:
     description: 'Test suite name for the header (e.g. "E2E Ginkgo Nightly Tests"). Keep under ~130 chars — Slack header blocks have a 150-char limit and the status suffix takes ~15 chars.'
     required: true
   status:
-    description: 'Run status, typically `needs.<job>.result` or `job.status`. `success` and `failure` notify; `cancelled` and `skipped` are treated as no-ops and send nothing.'
+    description: 'Run status, typically `needs.<job>.result` or `job.status`. `success` and `failure` notify; `cancelled` and `skipped` are treated as no-ops and send nothing. Use `info` for a standalone informational notice (e.g. a deploy) that always notifies with no pass/fail suffix.'
     required: true
   details:
     description: 'Markdown text appended after the build URL (test results, versions, artifact links, etc.)'

.github/actions/ci-test-notify/build-payload.sh

@@ -10,10 +10,14 @@ case "$STATUS" in
   failure)    EMOJI="❌"; STATUS_TEXT="Failed" ;;
   cancelled)  EMOJI="⚠️"; STATUS_TEXT="Cancelled" ;;
   skipped)    EMOJI="⏭️"; STATUS_TEXT="Skipped" ;;
+  info)       EMOJI="🚀"; STATUS_TEXT="" ;;
   *)          EMOJI="❓"; STATUS_TEXT="Unknown ($STATUS)" ;;
 esac
 
-HEADER="${EMOJI} ${TEST_NAME} ${STATUS_TEXT}"
+# `info` carries no pass/fail meaning, so it gets no status suffix; every other
+# status appends one (" Success", " Failed", …). Keep the space inside the
+# expansion so an empty suffix leaves no trailing whitespace in the header.
+HEADER="${EMOJI} ${TEST_NAME}${STATUS_TEXT:+ ${STATUS_TEXT}}"
 
 # Slack header blocks reject >150 chars
 if [[ ${#HEADER} -gt 150 ]]; then

.github/actions/ci-test-notify/should-notify.sh

@@ -10,6 +10,10 @@ set -euo pipefail
 # (or superseded), and a skipped job never executed. Neither warrants a Slack
 # alert, so both are silenced here rather than in every caller.
 #
+# `info` is a status callers set deliberately for a standalone informational
+# notice (e.g. a release candidate landing in staging) rather than a run
+# conclusion; it is not a no-op and always notifies when a webhook is present.
+#
 # An empty webhook (fork PRs, where secrets are unavailable) also suppresses
 # the notification, same as before.
 #

.github/actions/ci-test-notify/test/build-payload.bats

@@ -48,6 +48,13 @@ payload_field() {
   [[ "$(payload_field '.text')" == *"Cancelled"* ]]
 }
 
+@test "info status uses rocket emoji and no status suffix" {
+  STATUS="info" TEST_NAME="Deployed to staging" run bash "$SCRIPT"
+  [ "$status" -eq 0 ]
+  # Exact match asserts there is no trailing status word or whitespace.
+  [ "$(payload_field '.blocks[0].text.text')" = "🚀 Deployed to staging" ]
+}
+
 @test "skipped status produces correct emoji and text" {
   STATUS="skipped" run bash "$SCRIPT"
   [ "$status" -eq 0 ]

.github/actions/ci-test-notify/test/should-notify.bats

@@ -37,6 +37,12 @@ notify_value() {
   [ "$(notify_value)" = "true" ]
 }
 
+@test "info notifies" {
+  STATUS="info" run bash "$SCRIPT"
+  [ "$status" -eq 0 ]
+  [ "$(notify_value)" = "true" ]
+}
+
 # --- Statuses that must stay silent (the bug this fixes) ---
 
 @test "cancelled does not notify" {