Skip to content

chore(submissions): auto outreach run 2026-08-11 17:17 - #31

Open
bucabay wants to merge 1 commit into
mainfrom
submissions/auto-2026-08-11-1717
Open

chore(submissions): auto outreach run 2026-08-11 17:17#31
bucabay wants to merge 1 commit into
mainfrom
submissions/auto-2026-08-11-1717

Conversation

@bucabay

@bucabay bucabay commented Aug 11, 2026

Copy link
Copy Markdown

Auto outreach run — 2026-08-11 17:17 UTC (act for real; DRY_RUN unset)

Reply drafts queued for Gabe: none this run (no emails sent, no replies triggered).
(Note: a pre-existing unrelated draft r_68b3e82e from the separate reply-followup agent re:
Programming Digest advertising is sitting in ~/.mailkite-cron/replies/ — not from this workflow.)


🎉 Reconciliation win — 2 pending PRs merged → LIVE

The mandatory fleet-wide dedupe scan (gh search prs --author bucabay) caught two awesome-list
PRs that merged since the last reconciliation
. Both verified to render in their merged READMEs:

Venue PR Merged Listing
officialrajdeepsingh/awesome-nextjs (707★) #88 2026-08-11 10:45 UTC (today) README line 1532nd confirmed listing
giovannism20/awesome-supabase (41★) #15 2026-08-10 22:12 UTC README line 773rd confirmed listing

3 listings now LIVE total (those two + bytefer/awesome-shadcn-ui #29, merged 2026-07-30).
All other pending awesome-list PRs re-checked OPEN; no new closes.

Researched

Swept nextjs / saas / tailwind / shadcn / drizzle / stripe / supabase / typescript / react / monorepo
awesome-lists + adjacent-tech (vercel-native, RSC, react-19) + template directories. Every strong-fit
git-PR venue is already acted-on
— the surface is saturated. New skips documented in the doc:

  • henryoman/awesome-vercel-native (12★, active) — Vercel Native SDK only; our standard Next.js
    starter isn't built on it → category mismatch.
  • birobirobiro/awesome-shadcn-ui-site (16★) — the website renderer for awesome-shadcn-ui (already PR'd #554); duplicate.
  • amanbolat/awesome-postgres-with-stars (0★, 1 day old) — Postgres tools, no starter section.
  • Plus stale/category-mismatch lists (brookshi/awesome-typescript-projects, itsdouges/awesome-typescript-ecosystem, CodelyTV/awesome-typescript-examples, awesome-vercel-alternatives ×3, lazylagom/*, Correia-jpv/fucking-awesome-* mirrors).

External PRs opened

0 (cap ≤3). No new git-PR venue cleared the bar — quality over volume.

Emails sent

0 (cap ≤5). No submission venue surfaced a public contact email this cycle (all Tier 2/3 are form/account-gated).

Manual added (Tier 3)

  • saasboilerplates.com — curated "best SaaS boilerplates" directory
    with a Next.js category (~12 listings).
    Free but account-gated (/submit-listing/ → 302 → /join/). Not listing us yet. Step-by-step
    instructions added to the Tier 3 table.

Flagged for human

  • saasboilerplates.com — needs a human to create the (free) account and submit to the Next.js
    category (agent can't cross the login wall).
  • Standing flags remain: aniftyco/awesome-tailwindcss (AI-PR ban — hand-submit), indiedev.tools,
    madewithshadcn.com, openalternative.co, starter.dev (all login/browser-only).

No external actions taken this run besides documentation. Source of truth: docs/SUBMISSIONS.md.

Reconciliation win run. Mandatory fleet dedupe (gh search prs --author bucabay)
found 2 pending awesome-list PRs MERGED since last reconciliation -> both now LIVE:
- officialrajdeepsingh/awesome-nextjs #88 (merged 2026-08-11 10:45Z) -- 2nd listing
- giovannism20/awesome-supabase #15 (merged 2026-08-10 22:12Z) -- 3rd listing

3 listings LIVE total (those two + bytefer/awesome-shadcn-ui #29).

New Tier 3 venue (manual/login-gated, FREE): saasboilerplates.com (Next.js category).
No new external PRs (cap <=3, used 0); no emails (cap <=5, used 0). Quality over volume.
@vercel

vercel Bot commented Aug 11, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
saas-nextjs-starter Ready Ready Preview Aug 11, 2026 5:25pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant