slackapi / slackapi/slack-github-action

Feature Request: Allow sending multiple messages at once

Open
#358 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement question
Dominant language
JavaScript
Stars
1.3k
Forks
200
Avg merge
2h 59m
Merged PRs (30d)
6

Description

Description

We generate workflow summaries from GHA and format each job as a Block, then post them to a notification channel for job status notifications. Recently, we encountered an issue where some workflows had more than 50 jobs. This exceeds the maximum number of blocks we can post at once. That is reasonable, and our solution is to generate multiple messages and post them in a thread. We do not always know how many messages we must submit since the summary is performed in a shared workflow. In order to do this I am left with 3 bad options:

  1. Send each message as part of a matrix job; this means each message consumes a self-hosted ARC runner, which seems excessive
  2. Fork the action ourselves and add support
  3. Do not use the action and fall back to making API calls ourselves

It would be great if there were some way of passing in multiple messages.

What type of issue is this? (place an x in one of the [ ])
  • bug
  • enhancement (feature request)
  • question
  • documentation related
  • example code related
  • testing related
  • discussion
Requirements (place an x in each of the [ ])
  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or entry points; begin by locating the GitHub Action's message submission path and its shared-workflow inputs. Compare the current single-message behavior with the requested multiple-message and threaded-posting flow, and define completion as supporting an unknown number of messages without requiring separate matrix jobs.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, javascript
Domain
ci-cd, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.