CyberCLI
← All notification channels

GitHub / GitLab issues

Pro BYO Ticketing Planned

Turn a verdict into a tracked issue — where your engineers already work.

Open + sync an issue per case. The technical team's ticket system.

Where to get it

Your GitHub/GitLab repo (cloud or self-hosted GitLab/Forgejo) + a scoped token.

Install / what you need

No install. You need a repo + a fine-scoped personal/project access token.

How to connect

  1. 1 Create a scoped token (issues:write) for the target repo.
  2. 2 Open the dashboard's Notifications panel → Add destination → choose github or gitlab, fill in the repo + token.
  3. 3 Cases open an issue; updates sync; closing the case closes the issue.

When you'd use it

Track incidents where the team already works.
Self-hosted GitLab/Forgejo = sovereign ticketing.
DevSecOps audit trail.
Sovereignty

Point it at self-hosted GitLab or Forgejo and the ticket trail stays entirely on your infrastructure.

Who notifies through it

Herald — the Guild's voice role — routes alerts, daily digests, and AI verdicts here, on a per-CYCON-state matrix you control. CYCON 1/2 alerts repeat until an operator acks.

The Guild →

Go deeper