liquidvotingio / liquidvotingio/api
Build notifications on slack
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 17
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
It'd be great to track build statuses on #github-dev-activity, specially since we need act quickly on smoke test failures (either reverting the failing commit or submitting a fix)
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 files, tests, or entry points. Start by identifying how builds and smoke-test failures are currently tracked, then determine how build statuses should be published to #github-dev-activity. Done means the channel receives timely status notifications that support responding to smoke-test failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100