GITHUB_REACTION_POLL: bound the poll by message age

Open Beginner friendly
#102 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, typescript
Domain
api, backend, databases

Research direction

Start at the handleGithubReactionPoll entry point and inspect the message.findMany where-clause. Add the recent createdAt window described in the issue, then verify that unreplied messages older than the window are excluded while recent messages remain eligible for reaction polling.

Written by the indexing model from the issue text.

Description

area: integrations roadmap roadmap: later

Follow-up from #101 review (jerelvelarde).

handleGithubReactionPoll's message.findMany has no createdAt cutoff. Any AI-generated GitHub comment that never receives a reaction stays feedback: null forever and is re-polled every 24h indefinitely, so GitHub API calls grow without bound over months.

Fix: add a createdAt >= now - N days filter (e.g. 14–30d) to the findMany where-clause so reaction polling only covers a recent window. A reporter who reacts months later is an acceptable miss.

Slow-burn only, zero day-1 impact — deferred out of #101 intentionally.

Dominant language
TypeScript
Stars
7
Forks
3
Avg merge
7d 16h
Merged PRs (30d)
15

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CopilotKit/outpost

All issues in CopilotKit/outpost

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.