slackapi / slackapi/slack-github-action
📖 Documentation: Include examples preparing slack message with conditional logic
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 200
- Avg merge
- 2h 59m
- Merged PRs (30d)
- 6
Description
Every couple of years I have trouble resolving the same issue: Slack messages with blocks that appear conditionally. I think it would help a lot of people if the documentation contained such examples. For example, a section that appears only if the test results failed. Or a section that appears only if the workflow was invoked manually.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no documentation file or test. Start by finding the action's documentation entry point and existing Slack message examples, then check how GitHub Actions conditional expressions are represented; done means adding examples for failed test results and manually invoked workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100