Skip to content

chore(submissions): auto outreach run 2026-08-06 17:17 - #19

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

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

Conversation

@bucabay

@bucabay bucabay commented Aug 6, 2026

Copy link
Copy Markdown

Auto outreach run — 2026-08-06 17:17 UTC (live, not DRY_RUN)

Reply drafts queued for Gabe: none

Headline: docs re-synced with reality (fleet-dedupe rule paid off)

A full gh search prs --author bucabay --state open sweep found 9 external
PRs
listing this template across awesome-* lists, opened 2026-07-29 → 2026-08-05
by a sibling cron + earlier runs without ever being logged in SUBMISSIONS.md.
All 9 are now recorded (submission log + Tier 1 table, status [~]). Highest reach
is brillout/awesome-react-components at 48.1k★ (PR #632).

Venue PR date
brillout/awesome-react-components 48.1k #632 08-03
semlinker/awesome-typescript 4.0k #177 07-31
xcomptek/awesome-saas-boilerplates 3.1k #222 07-29
iAmCorey/awesome-indie-hacker-tools 1.4k #158 08-02
officialrajdeepsingh/awesome-nextjs 707 #88 08-03
lyqht/awesome-supabase 479 #62 08-01
bytefer/awesome-nextjs 71 #23 07-31
giovannism20/awesome-supabase 41 #15 08-05
y-h-v-h/shadverse 28 #3 08-05

(The other bucabay PRs surfaced by the sweep — novu, boxyhq, better-auth, MCP
registries, awesome-opensource-email — are MailKite-product outreach from a
different cron, not saas-startup-template listings, so they're out of scope for
this doc.)

New external PRs opened: 0

The git-PR space is saturated by the sibling cron — every high-value fitting
awesome-* list already has an open PR. Remaining candidates from this run's
research are stale (awesome-monorepo 5.8k★ last pushed 2024-08), low-reach, or
off-topic (SaaS services/products lists vs boilerplates; awesome-selfhosted
311k★ is for self-hostable apps, not templates). Quality over volume → no new PRs.

Emails sent: 0

No new high-value venue with a public contact email that isn't already PR'd.
Cold-emailing when everywhere's already listed would be duplicative.

Flagged for human (held, not acted)

  • bytefer/awesome-shadcn-ui (722★, active) — held: shadcn space already has 2
    open PRs (awesome-shadcn-ui #554, shadverse chore(submissions): auto outreach run 2026-07-30 17:17 #3); a 3rd in the same window reads
    as spam. Revisit once those are reviewed.
  • 2-fly-4-ai/awesome-shadcnui (555★, ~14 mo stale) — same reason.
  • Chase the 11 open PRs — none merged yet; the highest-value ones
    (brillout/awesome-react-components, xcomptek/awesome-saas-boilerplates,
    semlinker/awesome-typescript) are worth a gentle human nudge.

Verified still-pending

The 2 originally-logged PRs remain OPEN (not merged, not closed):
awesome-shadcn-ui #554,
awesome-nextjs #536.

Diff: docs/SUBMISSIONS.md only.

A full `gh search prs --author bucabay --state open` found 9 external PRs
listing the saas-startup template across awesome-* lists (Next.js, TypeScript,
React, shadcn, Supabase, SaaS-boilerplate, indie) opened 2026-07-29..08-05 by a
sibling cron + earlier runs WITHOUT being logged here.

Recorded all 9 in the submission log + Tier 1 table (status [~]). Highest reach:
brillout/awesome-react-components (48.1k★).

No new external PR opened: every high-value fitting list is already covered;
remainder are stale / low-reach / off-topic (SaaS services vs boilerplates) /
vendor-specific. Flagged 2 extra shadcn lists (bytefer/awesome-shadcn-ui 722★,
2-fly-4-ai/awesome-shadcnui 555★) as held — shadcn space already has 2 open PRs.
@vercel

vercel Bot commented Aug 6, 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 6, 2026 5:23pm

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