Repository navigation
perf: parallelize digest generation - #67
Conversation
Signed-off-by: Arnab Nandy <arnab_nandy7@yahoo.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8a865ddf75
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| scoreIssue( | ||
| issue, | ||
| repository, | ||
| undefined, | ||
| Boolean(getHacktoberfestSource(issue, repository)), |
There was a problem hiding this comment.
Apply the portal's claimed-issue penalty to alert scores
For every assigned issue, this passes undefined as helpStatus, so scoreIssue omits its 25-point claimed penalty. The portal path explicitly converts assigned issues to helpStatus = "claimed" before calling the same scorer, meaning repository-alert emails now advertise a quality score 25 points higher than the portal for the same assigned issue. Derive at least the known assigned status here before scoring.
Useful? React with 👍 / 👎.



Summary
Adds portal scoring information to digest emails and reduces email-generation latency by parallelizing independent network and database operations.
Changes
Email behavior
Weekly recommendations now display:
Repository alerts now display:
Performance
Digest generation previously serialized several independent operations. Weekly-search generation, repository-alert generation, repository metadata enrichment, and post-delivery persistence now run concurrently where safe.