Remove the repo-content domain (repoContentSchema and its 7 supporting schemas/types) from @tripwire/contracts. The feature was deliberately retired in 68608e0 ("tripwire doesn't re-render github — owner decision"), which deleted the demo's repo-content routes, components, mock data, and lib files. This contract file was left behind with no production consumers — only a test-only import of repoContentSchema remained. The barrel re-export and the test assertion are removed as cascading cleanup.
Dead Code PRs can be configured here.
The latest updates on your projects. Learn more about Unkey Deploy
| Name | Status | Preview | Inspect | Updated (UTC) |
|---|---|---|---|---|
| tripwire / web (preview) | Ready | Visit Preview | Inspect | Nov 6, 2026 10:14am |
Blocked. See the comment.
@detail-app[bot], Tripwire blocked this change request.
Rate limit: You opened 50 change requests in a short time. Wait before you open another.
This result is out of date. See the newer comment below.
Capy found no issues.
Re: https://github.com/Boring-Software-Inc/v2/pull/178#issuecomment-6682434302\n\nAcknowledged. This is a Tripwire rate-limit block, not a code issue — a new commit won't change it. The repo's own check CI is green, the PR is mergeable, and the diff is a straightforward dead-code removal (1 add / 102 deletions in packages/contracts/src/repo-content.ts + barrel/test cleanup). Leaving this for a maintainer to decide whether to merge despite the Tripwire block.
@detail-app[bot], Tripwire now passes this change request.
Re: github.com/Boring-Software-Inc/…/178
Acknowledged. This is the same Tripwire rate-limit block described in github.com/Boring-Software-Inc/…/178 — not a code issue, and a new commit will not change it. The repo's own check CI is green and the PR is mergeable. Leaving for a maintainer to decide whether to merge despite the Tripwire block.
Sign in to comment.
