chore(submissions): auto outreach run 2026-08-03 21:17 - #11
Open
bucabay wants to merge 3 commits into
Open
Conversation
added 3 commits
August 2, 2026 04:26
- Acted: opened PR #158 to iAmCorey/awesome-indie-hacker-tools (模板/Templates section, 1395★, MIT, actively merges) — its templates section already lists our paid competitors; we fit as the free/OSS option. - Status: sorrycc/awesome-javascript #1133 was closed w/o merge -> flipped to [-] rejected. - Re-verified 9 other prior PRs still open. - Researched+skipped 8 more venues (dead lists / wrong-shape / tiny reach) -- see backlog. - No emails (PR-based venues; pestering curators violates quality-over-volume). Note: main's SUBMISSIONS.md was stale (94 lines) because prior run PRs (#2-#8) were never merged. This branch rebases the doc onto the latest accumulated state (163 lines) + this run's delta, so it is self-contained -- merge this PR and close #2-#8 as superseded.
- Opened PR #88 to officialrajdeepsingh/awesome-nextjs (708★, ## Next.js boilerplate) - Researched & skipped 6 new non-fitting venues (re50urces/Awesome-NextJs dead, mahseema/awesome-saas-directories wrong shape, tyaga001/awesome-neon stale, etc.) - Re-checked 10 prior pending PRs — all still open (11 pending total) - 0 emails (PR-based lists; cold-emailing curators = pestering) - Carries forward accumulated prior-run updates not yet on main
- Opened 1 external PR: brillout/awesome-react-components #632 (48.0k★ curated React-components list; ## Boilerplate section; CC0; 1:1 add MailKite + remove archived nwb per CONTRIBUTING keep-fresh rule). - Research (5th pass): markodenic/web-development-resources (8k★, fresh, actively merges) skipped — wrong shape (utilities/static-templates list, no full-stack/SaaS section; 'automated bot submissions' caution). lincolixavier/awesome-indie-hackers (no license, no template section), devton/awesome-postgresql (tooling only), itsdouges/awesome-typescript-ecosystem, tiny awesome-vercel/nextjs variants — all skipped with reasons. - Re-checked 11 prior pending external PRs: all still OPEN, no merges/closures. - No emails (same pestering-not-outreach discipline). No paid/AI-ban flags this 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.
Auto outreach run — 2026-08-03 21:17 UTC
External PR opened (1 of ≤3)
## Boilerplatesection ("scaffold / starter kit / stack ensemble"), placed alphabetically. CONTRIBUTING has no AI-PR ban but requires that any add also remove one un-awesome entry → this PR is a 1:1 add/remove: it adds us and removesinsin/nwb(that repo is archived). Disclosed honestly in the PR body that the project is new/low-stars. Note: merge cadence is bursty (last batch 2026-01-26 merged 16 outside PRs; 57 open), so it may wait — but it's the highest-reach venue we've tapped.Dedup guard (fleet rule): ran both
gh pr list --search mailkiteand--author bucabayon the target → clean. CONTRIBUTING re-checked for an AI-PR ban right before acting → none.Emails sent
Manual / flagged-for-human
None new this run. (No paid placements or AI-PR-ban blocks encountered.)
Research summary (5th pass, 4-hr cadence)
Searched GitHub by topic for: awesome-{nextjs, saas-boilerplate, shadcn, tailwindcss, drizzle, turborepo, stripe, postgres, react-rsc, oauth, authentication, indie-hacker, maker, supabase, react, selfhosted, open-source-apps, web-development, typescript, fullstack, webdev, vercel, transactional-email}, plus starter-kit/boilerplate terms. After filtering out venues already in SUBMISSIONS.md, one new candidate cleared the bar and was acted on (brillout, above). Notable skipped (all verified live this run):
The high-quality git-PR well remains largely tapped — brillout was the one genuine high-reach find with a fitting section this pass.
Pending PRs — status recheck
Re-checked all 11 prior pending external PRs → all still OPEN, no new merges or closures since the 13:17 pass. (12 pending total now, counting #632.) One prior listing is live: bytefer/awesome-shadcn-ui #29 (merged 2026-07-30).
Note on branch base
main'sdocs/SUBMISSIONS.mdis behind (prior cron-run PRs #1–#10 are still open/unmerged, so the accumulated log/tier/backlog content lives only on those branches). This branch is based on the latest of those (submissions/auto-2026-08-03-1317, PR #10) so the history is preserved; merging this PR supersedes #10.