QRun-IO/qqq-orb
Archived
2
0 Fork 0
Code Issues 6 Actions Packages Projects Releases 17 Wiki Activity

Add slack support to the orb workflows #2

New Issue
Open
opened 2025-09-20 12:15:11 +00:00 by KofTwentyTwo · 1 comment
KofTwentyTwo commented 2025-09-20 12:15:11 +00:00 (Migrated from github.com)
Copy link
Copy source

🚀 Feature Description

Add slack support to the orb workflows, provide messages to developers without needing to log into circleci

💡 Motivation

Just a nice to have QOL improvement for engineering

📋 Detailed Description

  • What: What should the feature do?
    • Integrate with Slack to send status messages about workflows running to the team or the developer that triggered the workflow.
  • Why: Why is this feature important?
    • Nice improvement for developers
  • How: How should it work?
    • Optional param on the workflow settings into the orb (on or off)
    • via a Slack App and webhooks into that app most likely
    • At the repo level, you should be able to define which teams (slack channels) should be told about non-developer messages
  • When: When would this be used?
    • Just during development

🎯 Use Cases

Describe specific use cases for this feature:

  1. Feature and Test Only Workflows: send status and result messages to the developer that inited the workflow via slack (qqq slack)
  2. Successful Main/RC/Develop Workflows: send status and result messages to the qqq-orb channel
  3. Unsuccessful Main/RC/Develop Workflows: send status and result messages to the developer directly

📊 Priority

  • Low - Nice to have
  • Medium - Would be helpful
  • High - Important for workflow
  • Critical - Blocking current work
## 🚀 Feature Description Add slack support to the orb workflows, provide messages to developers without needing to log into circleci ## 💡 Motivation Just a nice to have QOL improvement for engineering ## 📋 Detailed Description - **What**: What should the feature do? - Integrate with Slack to send status messages about workflows running to the team or the developer that triggered the workflow. - **Why**: Why is this feature important? - Nice improvement for developers - **How**: How should it work? - Optional param on the workflow settings into the orb (on or off) - via a Slack App and webhooks into that app most likely - At the repo level, you should be able to define which teams (slack channels) should be told about non-developer messages - **When**: When would this be used? - Just during development ## 🎯 Use Cases Describe specific use cases for this feature: 1. **Feature and Test Only Workflows**: send status and result messages to the developer that inited the workflow via slack (qqq slack) 2. **Successful Main/RC/Develop Workflows**: send status and result messages to the qqq-orb channel 3. **Unsuccessful Main/RC/Develop Workflows**: send status and result messages to the developer directly ## 📊 Priority - [X] Low - Nice to have - [ ] Medium - Would be helpful - [ ] High - Important for workflow - [ ] Critical - Blocking current work
darinkelkhoff commented 2025-09-30 11:53:47 +00:00 (Migrated from github.com)
Copy link
Copy source

I would personally un-request this feature.

At ColdTrack we added these (CI -> slack notifications), and for the first day they seemed great; by the end of the first week they were just noise that annoyed me; by week two i muted the channel and never looked at it again.

Now that's just my experience - so if others would want this, I'm not here to say "no". I'm just used to the workflows I have (maybe most saliently a swiftbar plugin i wrote that pings circleci's api, to passively give me a version of this), so, anyway, those are my 2 pennies.

I would personally un-request this feature. At ColdTrack we added these (CI -> slack notifications), and for the first day they seemed great; by the end of the first week they were just noise that annoyed me; by week two i muted the channel and never looked at it again. Now that's just my experience - so if others would want this, I'm not here to say "no". I'm just used to the workflows I have (maybe most saliently a swiftbar plugin i wrote that pings circleci's api, to passively give me a version of this), so, anyway, those are my 2 pennies.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No labels enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QRun-IO/qqq-orb#2