srlabs / srlabs/ziggy

Fuzzer could send status notification on crash / daily

Open
#2 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
87
Forks
11
Avg merge
11h 29m
Merged PRs (30d)
2

Description

Ziggy could be given an API key through ENV or the CLI, which it could then use to send out notifications to the user.

Ideas for the notification platform include:

  • Discord DMs (probably requires creating a "discord bot")
  • emails (probably requires using a third party service)
  • GitHub issues (requires a target repository)

Contributor guide

No contributing guide indexed for this repository

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

No files, tests, or implementation entry points are named. Start by reviewing Ziggy's existing CLI and environment configuration, then define one notification platform and its crash or daily trigger behavior. Done means the selected notification path, credential handling, and supported notification events are specified and implemented with tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.