Documentation
Using Ziggy
Ziggy filters through noisy pull requests so maintainers see the submissions that matter first. It reads each PR, checks the contributor's GitHub history, scores contributor trust and code risk, and keeps spam, slop, copycats, and sensitive-path changes out of the main review path. That makes open rewards safer: label an issue with ziggytest:100USDC, keep the final decision, and Pvium pays only the work you approve.
Issue Labels
Add these labels to GitHub issues to tell Ziggy which rewards and PR windows apply.
ziggytest:50USDCziggytest:50 USDCziggytest:25ziggytest:window:1h| Label | Purpose | Notes |
|---|---|---|
ziggytest:<amount><currency> | Registers a bounty for the issue. | Example: ziggytest:100USDC. Amounts may be whole or decimal values. |
ziggytest:<amount> | Registers a USDC bounty. | Currency defaults to USDC when omitted. |
ziggytest:window:<duration> | Sets the PR window for one issue. | Overrides the repository default from settings. Supported units are m, h, and d. |
PR Window
PRs submitted after the window will not be shown on the dashboard by default.
- Use
ziggytest:window:30m,ziggytest:window:1h, orziggytest:window:1don an issue to set an issue-specific window. - Minutes, hours, and days are supported. Days are the largest unit, so use
7dinstead of1w. - When Ziggy registers the bounty, it comments on the issue with the reward and deadline so contributors can see the cutoff.
Force Review
Maintainers can ask Ziggy to analyze a rate-limited PR without changing repository-wide limits.
- Comment
ziggy:force-reviewon a pull request to run analysis once despite volume or rate limits. - Only maintainers can force review. Ziggy checks GitHub permissions before running the command.
- Force review does not force payout. It only spends analysis on that PR so maintainers get the usual Ziggy assessment.
- Hard safety limits still apply, including PRs that are too large by changed files or changed lines.
Dashboard
Use the dashboard to review issues that have a reward without opening every pull request on GitHub first.
- Open /dashboard and sign in with GitHub. Ziggy only shows repositories where you have maintainer access.
- Start with the Bounty queue. Issues are grouped with their related PRs so you can inspect the strongest submissions first.
- Use score, status, and duplicate signals to decide which PRs deserve review. Low-signal PRs stay out of the main queue by default.
- Open the PR details when a submission looks promising or risky. Ziggy is decision support; maintainers still make the final call.
- Use Recent rewards and Top contributors to audit payout history and contributor performance across repositories.
Settings Page
Repository settings live at /dashboard/settings.
- Repository Access shows the repositories where Ziggy is installed and your GitHub account has maintainer access.
- Default PR Window sets a fallback PR window per repository. Leave it blank for no default window.
- Issue labels such as
ziggytest:window:1hoverride the repository default for that issue. - Settings updates are saved in place and confirmed with a top-right notification.