Skip to content

fix: fail incomplete pr content fetches#38

Open
Desel72 wants to merge 1 commit into
entrius:testfrom
Desel72:fix/incomplete-pr-content-status-2
Open

fix: fail incomplete pr content fetches#38
Desel72 wants to merge 1 commit into
entrius:testfrom
Desel72:fix/incomplete-pr-content-status-2

Conversation

@Desel72
Copy link
Copy Markdown

@Desel72 Desel72 commented May 12, 2026

Summary

Keep scoring_data_stored false when PR file content fetching cannot complete.

  • Throw when a PR file fetch has no headSha, instead of returning before content fetch.
  • Throw when GraphQL content fetching still fails at the minimum batch size, instead of skipping that batch and continuing.
  • Let the existing BullMQ retry/failure path handle incomplete fetches rather than marking the PR generation complete.

Related Issues

Closes #37

Type of Change

  • Bug fix
  • New feature
  • Refactor
  • Documentation
  • Other (describe below)

Testing

  • npm run build
  • npm run lint
  • npm run format:check
  • git diff --check

Checklist

  • I have read the Contributing Guide
  • Code builds without errors
  • New and existing tests pass (if applicable)
  • Documentation updated (if applicable)
  • No unnecessary dependencies added

@xiao-xiao-mao xiao-xiao-mao Bot added the bug Something isn't working label May 12, 2026
@Desel72 Desel72 closed this May 12, 2026
@Desel72 Desel72 reopened this May 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] PR file fetch can mark scoring data complete after content fetch is skipped

1 participant