Ziggy should support automation/notification
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 87
- Forks
- 11
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 2
Description
automation:
- If
cargo ziggy buildfails then send a notification - If
cargo ziggy runfails then send a notification - If a crash is found, send a notification (once per day only, collect them)
- If no coverage is found for X minutes, send a notification (once per day)
Notification: execute a specified OS command.
Maybe something like:
-B command
-R command
-C command
-S 30:command (stalled coverage for 30 minutes: execute command once per day)
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing the cargo ziggy build and cargo ziggy run command entry points. Define how specified OS commands receive build failures, run failures, crashes, and stalled-coverage events, including the once-per-day collection behavior. Done means these notifications work for the requested event types and command-line options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100