# I built a small daily digest of trending GitHub repos. I'd love your feedback > Source: > Published: 2026-11-04 13:50:02+00:00 I check GitHub Trending most mornings, and I kept losing track of what I'd seen the day before. So I started a small side project to keep a dated record for myself: [Northline Signal](https://northline-signal-2026.web.app/). It's a solo project and still pretty rough. I'm posting here mostly to learn from people who follow open source more closely than I do. ## What it is Each day gets its own page with the repos that were trending that morning. Today's page, for example, is [November 4, 2026](https://northline-signal-2026.web.app/day/2026-11-04/). It has 13 projects, from `thedotmack/claude-mem` to `vercel-labs/agent-desktop` and `floci-io/floci`. Each entry shows: - total stars and stars gained that day - a rough category (AI, Automation, Infrastructure, Data, and so on) - a one-to-two sentence summary of what the project does Every project also has its own page, like [vercel-labs/agent-desktop](https://northline-signal-2026.web.app/p/vercel-labs/agent-desktop/). That page has the main language, a link to the repo, the dates it showed up, and a short note on what a developer might actually take from it. There's also an [Explore page](https://northline-signal-2026.web.app/explore) where you can search across past days and filter by category or language, which helps when you're trying to find "that Rust CLI from last week". There's also a [Chinese version](https://signal.wujunch8.com/), since a lot of my friends read in Chinese. ## How it works The setup is deliberately small: - A GitHub Actions workflow runs every day at 09:00 Beijing time (01:00 UTC) and fetches the trending list. - The same workflow asks Gemini to write the summary and the short note for each project, then commits the result as a JSON file per day. - The site is Vite + React + TypeScript. It's built as static pages and deployed to Firebase Hosting. No database, no server. The content is just files in the repo, so adding a new day means pushing a new JSON file. ## What I'm still figuring out Quite a lot, honestly: - **The notes sometimes read generic.** I've spent more time than I expected on prompts so the notes sound like a person who skimmed the README, not a press release. Some days it works. Other days you get the same sentence shape thirteen times, and once or twice bits of the prompt leaked into the output. I'm still tuning it. - **Free-tier API limits.** I use the free Gemini tier, which often returns 503 or 429 at busy times. I added a fallback chain of models, but some notes still come out thinner than others. - **Scheduled runs aren't fully reliable.** At least once the cron didn't fire and I had to start the workflow by hand. - **Categories are fuzzy.** Is an agent plugin "AI" or "Automation"? I go back and forth. ## I'd really like your feedback If you have a minute to look around, I'd be grateful for any thoughts, especially: 1. Are the per-project notes useful, or would you rather just have the plain description? 2. What would make a digest like this worth checking regularly? Weekly roundups, a short "why it is trending" line, something else? 3. Does anything feel confusing or broken on mobile? I'm sure there are better ways to do parts of this, and I'd like to hear about them. Thanks for reading. Site: [https://northline-signal-2026.web.app/](https://northline-signal-2026.web.app/)