chore(submissions): auto outreach run 2026-08-06 05:17 - #18
Open
bucabay wants to merge 1 commit into
Open
Conversation
Doc-sync run triggered by the GitHub dedupe rule (fleet rule 2026-08-03). The pre-act dedupe check (gh pr list --search mailkite + --author bucabay) surfaced SIX prior awesome-list submissions opened 2026-07-29..08-03 by earlier sessions that were never recorded in docs/SUBMISSIONS.md: - bytefer/awesome-shadcn-ui PR #29 MERGED -> LIVE (## Saas) - xcomptek/awesome-saas-boilerplates PR #222 (open) - EinGuterWaran/awesome-opensource-boilerplates PR #52 (open) - officialrajdeepsingh/awesome-nextjs PR #88 (open) - lyqht/awesome-supabase PR #62 (open) - bytefer/awesome-nextjs PR #23 (open) [was tabled as a TODO] All six are now logged + added to Tier 1. bytefer/awesome-nextjs moved from [ ] todo -> [~] submitted. Research this run (nextjs/shadcn/saas/supabase/drizzle/stripe/turborepo/ monorepo/tailwind/open-source-saas) found NO new viable git-PR venue: every active, fitting, free list with reach already has an open/merged MailKite PR; the rest are stale (>6mo, not merging) or sub-10*. Those dead lists are recorded as [-] in Tier 1 to prevent re-research. 0 new external PRs / 0 emails (quality over volume; no clean live target). No DRY_RUN.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Autonomous submission-outreach run · 2026-08-06 05:17 UTC ·
DRY_RUNoff.TL;DR
0 new external PRs · 0 emails. This run was a doc-sync triggered by the pre-act dedupe check (fleet rule 2026-08-03), which caught 6 prior submissions that earlier sessions opened but never logged. Recording them (and the dead lists) is the whole change here.
What the dedupe rule caught (GitHub is source of truth)
Before acting on any candidate, ran
gh pr list -R <repo> --state all --search mailkiteand--author bucabay. Every high-reach git-PR venue already had a MailKite PR — none were indocs/SUBMISSIONS.md:[x]LIVE (README## Saas)[~][~][~][~][~](was tabled as[ ]todo)→ Without the dedupe rule, this run would have opened 6 duplicate PRs. None opened.
Research coverage (no new viable venue)
Searched awesome-* lists across: nextjs · shadcn-ui · saas-boilerplate · supabase · drizzle · stripe · turborepo · monorepo · tailwind · open-source-saas · boilerplate.
Every active, fitting, free list with meaningful reach is already covered above. New lists found were all stale (pushed >6mo, not merging outside PRs) or sub-10★ — recorded as
[-]in Tier 1 to prevent future re-research:Why no emails
All awesome-list maintainers expose PR channels (already used) — cold-emailing them would be redundant/spammy. No clearly-identified, high-quality, non-spammy email recipient surfaced. Per "when unsure, document as MANUAL, don't act" → 0 emails.
Flagged for human
Caps
PRs opened this run: 0/3 · Emails: 0/5. Within limits.