firecrawl / firecrawl/last30flames

GitHub person-mode: author-scoped queries when the topic is a person

Open
#7 0 comments 0 reactions 0 assignees View on GitHub
P2
Dominant language
TypeScript
Stars
38
Forks
8
PR merge metrics
No merged PRs in 30d

Description

last30days switches GitHub from keyword search to author-scoped queries when the topic is a person: PRs merged and merge rate, own repos with stars and README summaries, recent releases. That answers 'what are they shipping' rather than 'who mentioned this name in an issue'.

last30flames already uses the official GitHub API, so this is fully within constraints: detect (or accept via flag, e.g. `--github-user=steipete`) a GitHub login and query commits/PRs/repos/releases scoped to that author within the recency window, rendering them into the numbered context.

Contributor guide

Open the contributing guide

Research direction

Start by reading the existing last30days and last30flames GitHub API entry points to understand how topics, recency windows, and numbered context are handled. Trace the current keyword-search flow, then define the author-scoped behavior for commits, PRs, repositories, and releases, including the optional --github-user flag. Done means a person topic produces author-focused results within the recency window while other topics retain their existing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, typescript
Domain
api, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.