Skip to content

fix: dedupe GitHub App reports without push metadata - #84

Open
blalor wants to merge 1 commit into
wevm:mainfrom
blalor:blalor/fix-app-deduplication
Open

fix: dedupe GitHub App reports without push metadata#84
blalor wants to merge 1 commit into
wevm:mainfrom
blalor:blalor/fix-app-deduplication

Conversation

@blalor

@blalor blalor commented Aug 20, 2026

Copy link
Copy Markdown

What

Build the label-filtered issue index even when repos.get() does not report push access. Push access now controls only whether Frog expects labels to stick on newly created issues.

The unlabelled fallback also scans issues newest-first, so its 5,000-item ceiling includes recent reports.

Why

GitHub App installation tokens can create labelled issues while the repository response omits permissions.push. Frog 1.1.0 treats those repositories as unlabelled and scans their oldest 5,000 issues. In larger repositories, a repeated publish cannot find the recent issue and creates a duplicate.

Fixes #83.

Testing

  • Added coverage for a labelled issue when push access is not reported.
  • Updated the pagination regression to verify that a recent issue beyond the oldest 5,000 is found.
  • pnpm test: 45 files, 729 tests passed.
  • pnpm check:types passed.

@vercel

vercel Bot commented Aug 20, 2026

Copy link
Copy Markdown

@blalor is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GitHub App token fallback misses recent issues in large repositories

1 participant