Skip to content

extension-duplicate-check: Remove backend names from author messages - #15

Merged
0xdhrv merged 1 commit into
masterfrom
fix/duplicate-check-author-wording
Nov 2, 2026
Merged

0xdhrv merged 1 commit into
masterfrom
fix/duplicate-check-author-wording

Conversation

@0xdhrv

@0xdhrv 0xdhrv commented Nov 2, 2026

Copy link
Copy Markdown
Member

Authors shouldn't need to know how the duplicate check works, so the comment and job summary no longer name the scorer, TypeSafe, Jev, or Redash.

  • The score explanation is now one generic line: "Scores range from 0 to 1 and show how closely an existing extension matches this one."
  • Notes about skipped sources are plain: "Store extensions could not be checked this time." and "Open pull requests could not be checked this time."
  • When Jev fails and the check falls back to lexical, the comment no longer says so. The existing warning on the workflow run is now the only signal, so maintainers see it there.
  • A new test checks that the comment doesn't contain these terms.

To take effect, the workflow in raycast/extensions needs its pinned SHA bumped after this merges.

Tested locally: npm run typecheck, npm test (45 passed), npm run build.

The comment and job summary no longer mention the scorer, TypeSafe or Redash. Fallbacks stay visible to maintainers as workflow warnings.
@0xdhrv
0xdhrv merged commit 89056fd into master Nov 2, 2026
1 check passed
@0xdhrv
0xdhrv deleted the fix/duplicate-check-author-wording branch November 2, 2026 12:42
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.

1 participant