Use GitHub issue events as engineering context for a tracked bug. The connector receives observations; it never treats an issue closing as proof that a production fix reached a customer. Customer conversations and engineering issues keep separate lifecycles.
Create a repository connection
An unimpersonated workspace owner opens Product updates → Bug-to-fix loop → Engineering tracker on a bug.
- Choose New repository connection.
- Enter the repository's numeric ID and
owner/repositoryname. The numeric ID is the identity check; a renamed repository keeps that identity. For public repositories, GitHub'sGET https://api.github.com/repos/OWNER/REPOresponse includesid. For private repositories, use your authorized GitHub tooling to read that same repository metadata. - Leave Receive signed GitHub issue events selected and choose Connect repository.
- Copy the one-time signing secret into your GitHub webhook configuration. Frosvo seals its stored copy. Reloading or closing the dialog hides the displayed secret; it is not written to browser storage.
- Copy the displayed GitHub webhook payload URL. Reuse this connection for other bugs in the same repository; one webhook can route multiple issue bindings. A workspace supports up to 50 repository connections.
The repository numeric ID cannot be changed on an existing connection. Choose a new connection for another repository. Connection edits compare the saved revision; reload if another owner changed it. Explicit reload discards unsaved input and hides the one-time secret.
Configure the GitHub webhook
In the repository's webhook settings, create a webhook using:
- Payload URL: the URL displayed by Frosvo.
- Content type:
application/json. - Secret: the one-time signing secret from that connection.
- Events: select individual events and enable Issues. GitHub also sends a setup ping.
- SSL verification: enabled. Use your actual public HTTPS Frosvo address, not localhost or a private test address.
Review the latest delivery in GitHub. A valid ping updates Last authenticated ping in Frosvo after reload. That proves the signed endpoint was reached; it does not prove an issue is linked, a deployment happened, or a customer message was delivered. GitHub describes the signature format and repository webhook setup.
Bind an issue to a tracked bug
Select the saved repository connection, enter the exact GitHub issue number, and choose Save issue link. One issue maps to one tracked bug; attach all affected customer conversations to that bug. Different tracked bugs cannot claim the same repository issue number.
The issue's stable numeric ID is pinned when its first new signed observation arrives. The dialog shows Waiting for a signed issue observation until then. Create a genuine new issue edit after binding if you need a fresh observation. Older unlinked deliveries are not retroactively applied to a new binding.
Changing an issue identity invalidates the bug's confirmation. Saving an unchanged link preserves its observation. Remove issue link stops that binding, retains recorded event history and requires production verification to be reviewed. It does not delete the engineering issue or customer conversations.
Interpret observations safely
- Issue edits and repository renames use stable numeric identities. The observed repository name and issue title can change without silently switching to another issue.
- CLOSED is a GitHub source state. It never confirms a production fix or closes customer cases.
- A fresh open/reopen, deletion or conflicting identity can reopen a confirmed bug and invalidate pending fix notifications. Verify the actual production behavior before confirming again.
- Older source snapshots stay historical. Contradictory snapshots with tied source times become UNKNOWN and require review. Receipt time is distinct from the source's update time.
- Editing an issue that was already open does not itself invalidate a verified partial rollout. An observed closed-to-open transition can flag a missed regression event.
- Deleted or transferred issues are not silently rebound. Review the engineering issue and explicitly update its binding when required.
Use REPRODUCED and VERIFICATION_PENDING on the bug board to record intermediate work, or link the conversation to live incidents. Follow the release evidence and rollout guide to verify production and select recipients. This connector never queues a customer message by itself.
The dialog shows the 20 most recent tracker events. Workspace exports include retained connections, issue bindings and event metadata. Signing secrets, internal request digests and raw issue bodies are excluded. Bug/workspace deletion removes its associated records according to their ownership.
Rotation, disabling and troubleshooting
Save or reload pending changes before choosing Rotate GitHub signing secret. Update the GitHub webhook to the new secret immediately; the previous key is invalidated, and in-flight old configuration cannot publish an observation. Retrying a stored signed body with another delivery header cannot apply it twice.
To stop a repository, clear Receive signed GitHub issue events and save. Stored history remains; disabled endpoints refuse new deliveries. Disabling does not need to decrypt the existing key.
The receiver supports selected issue actions, a 1 MiB body limit and bounded body reading. Unsupported/malformed payloads, wrong identities, invalid signatures and oversized requests are refused. The per-connection limit is 600 requests per minute. Investigate failed deliveries and use GitHub's redelivery controls after fixing configuration or availability; do not assume a failed HTTP response will repair itself. See GitHub's webhook troubleshooting guide.
Operators must apply prisma/bug-tracker.sql and prisma/workspace-export-counts.sql alongside the bug-notification/evidence schema before upgrading all writers. Build from the updated Prisma schema. Keep the expanded export-count column on rollback; shortening it can corrupt JSON metadata. Repository setup and real GitHub delivery acceptance are required before treating a production connection as operational. Synthetic test events do not certify a real repository configuration.